Follow-up Comment #2, bug #26261 (project gforth):
Looking into this more, I've found that using SEE on built-in commands
somehow causes the "launchd" program to exit due to a segmentation fault, with
this near the top of the crash report:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bf7ffe80
Crashed Thread: 0
This explains the inability to open applications. Unfortunately, I still
have no idea exactly why this is happening. I have found that this problem
only occurs when Gforth is configured to be 64-bit; invoking "configure" with
no options leads to the creation of an executable without this problem, albeit
slightly slower and with smaller numbers. The only possible cause that I can
definitively rule out is Leopard's quarantining of downloaded files; when I
realized that the source & executable were quarantined, I removed the extended
attributes, only for the problem to persist.
I have no idea what differences could cause the problem to not occur for you,
though if you ask for any specific hardware or software details of my
computer, I can most likely give them to you.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?26261>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
bug-gforth mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/bug-gforth
