[Gc] Segmentation fault on Mac OSX intel
hans.boehm at hp.com
Mon Mar 20 17:58:47 PST 2006
I'm not sure whether there is somebody on this list with access to an
Intel Mac. As it stands, it's very hard to figure out what's going on
here. Does "make check" in the GC directory work correctly?
If so, it would be good to know what the arguments to cleanup are, and
exactly which assembly instruction is failing. Is it taking a wild
branch? Gc_cleanup::cleanup is a very small inlined function in
gc_cpp.h, which just invokes a destructor.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Andrea Cavalli
> Sent: Monday, March 20, 2006 7:21 AM
> To: gc at napali.hpl.hp.com
> Subject: [Gc] Segmentation fault on Mac OSX intel
> Code that works on Linux-intel and Mac OSX PPC generates
> segmentation fault on Mac OSX Intel.
> GC version 6.7 compiled with options --disable-shared
> --enable- cplusplus.
> GDB stack trace:
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_INVALID_ADDRESS at address: 0xfe6a868f
> 0x003ac029 in gc_cleanup::cleanup ()
> (gdb) bt
> #0 0x003ac029 in gc_cleanup::cleanup ()
> #1 0x000b6cb8 in GC_invoke_finalizers () at finalize.c:787
> #2 0x000b6d5c in GC_notify_or_invoke_finalizers () at finalize.c:844
> #3 0x000b77f5 in GC_generic_malloc (lb=8, k=1) at malloc.c:190
> #4 0x000b7b18 in GC_malloc (lb=8) at malloc.c:333
> #5 0x00bd13ee in eq_op_operator<int, int> ()
> #6 0x00be0b81 in ZObj::BinaryOperator<291>::apply ()
> #7 0x00be3018 in BinaryExp::eval ()
> #8 0x000b04bf in WhileBlock::eval ()
> #9 0x000a601b in print_exp ()
> #10 0x000a082d in zeta_parse ()
> #11 0x00002f02 in main ()
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc