New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Illegal Instruction on Mac Intel #4036
Comments
Comment author: @xavierleroy Probably a stack alignment issue: dyld_stub and various other C functions frame 0 and tell us the results. |
Comment author: dellaert OK, here it is: (gdb) r Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand. |
Comment author: @xavierleroy This is indeed a stack alignment problem. I'll track it down when |
Comment author: kentaur Is there anything I can do to help with tracking down this problem? I've access to MacBook Pro. |
Comment author: @xavierleroy Hello, I'm now the happy owner of a MacBook Pro, so I'm finally in a position Best regards,
|
Comment author: @xavierleroy Follow-up: I ran into a similar stack alignment problem with another Best regards,
|
Comment author: @xavierleroy Fixed in 3.09 branch. |
Original bug ID: 4036
Reporter: dellaert
Assigned to: @xavierleroy
Status: closed (set by @xavierleroy on 2006-07-18T07:36:58Z)
Resolution: fixed
Priority: normal
Severity: crash
Version: 3.09.2
Category: ~DO NOT USE (was: OCaml general)
Related to: #4114
Monitored by: kentaur
Bug description
when compiling natively on Mac Intel programs crash with "Illegal instruction". I know this has been reported before and supposedly resolved in 3.09.2, and indeed a small "hello world" program compiles and runs without problem. However, our real applications link with lablgtk and lablGL and various other libraries, and always crash (they run fine as bytecode). In two cases I ran gdb to see where it occurs, and both cases it was during the garbage collection. Below a backtrace...
Additional information
Here is a backtrace from gdb:
Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand.
0x8fe136e4 in __dyld_stub_binding_helper_interface ()
(gdb) bt
#0 0x8fe136e4 in __dyld_stub_binding_helper_interface ()
#1 0x00000000 in ?? ()
#2 0x0039479d in caml_process_pending_signals ()
#3 0x0039491f in caml_garbage_collection ()
#4 0x002509a0 in caml_call_gc ()
Previous frame inner to this frame (corrupt stack?)
(gdb) q
The text was updated successfully, but these errors were encountered: