Re[6]: [Gc] Segfault in GC_mark_from

Ivan Maidanski ivmai at mail.ru
Mon Oct 27 02:31:34 PST 2008


Hi!

Klaus Treichel <ktreichel at web.de> wrote:
> Hi,
> 
> > Please recompile the gc lib manually - type the following:
> > rm add_gc_prefix.c AmigaOS.c gcname.c if_mach.c if_not_there.c MacOS.c msvc_dbg.c setjmp_t.c threadlibs.c
> > gcc -c -g -Wall -Wno-uninitialized -D_REENTRANT -D_GNU_SOURCE -DALL_INTERIOR_POINTERS -DNO_EXECUTE_PERMISSION -DGC_ASSERTIONS -DGC_THREADS -I include -I libatomic_ops-1.2/src *.c libatomic_ops-1.2/src/atomic_ops.c
> > ar -crus libgc.so *.o
> > 
> > And don't turn on GC incremental mode (i.e. don't call GC_enable_incremental() or set GC_ENABLE_INCREMENTAL env var).
> > If You'd manage to reproduce the bug again with this config - let me know.
> 
> I sent a mail with our the detailed build settings.
> We don't use incremental collection.

Could You, please, try with the above (minimal) config? By doing so, You minimize the area where the bug resides.

> 
> This is a part og GC_dump() that i get on Cygwin with our test app.
> ....
> We didn't have any problem with this with libgc 6.8 but that seems to
> cause the problems with 7.1/7.2a1 now.

If so then try middle versions (with default config) until got same problem - gc7.0a7, gc7.0a9, gc7.0, gc7.1a2, gc7.1a2-r, gc7.1a3, gc7.1a3-24.

> 
> Klaus

Bye.



More information about the Gc mailing list