Wine & Boehm garbage collector

Vincent Béron vberon at
Fri Nov 22 19:56:01 CST 2002

Le jeu 21/11/2002 à 21:22, Alexandre Julliard a écrit :
> François-Denis Gonthier <fgonthier at> writes:
> > Apparently, the problem lies in Boehm GC, but before mailing Hans
> > about this (he can probably provide limited support only), I'd like
to hear
> > about the people that knows about the internals of Wine.
> It seems that seg fault is deliberate, it's trying to determine the
> end of the addressable space. So if you continue execution the signal
> should get handled; maybe this is what breaks, or maybe it's something
> else later on.

It's somewhere else:

Program received signal SIGSEGV, Segmentation fault.
0x405a54ab in GC_mark_from (mark_stack_top=0x80871b8,
    mark_stack_limit=0x808f0a8) at mark.c:647
647               deferred = *limit;
(gdb) bt
#0  0x405a54ab in GC_mark_from (mark_stack_top=0x80871b8,
    mark_stack=0x80870a8, mark_stack_limit=0x808f0a8) at mark.c:647
#1  0x405a51a0 in GC_mark_some (
"´\005\\@\034-\202 at h7[@(ÕY@´\005\\@L-\202@@ÙY@(ÕY at h7[@L-\202 at +ÙY@¯ÓZ@")
at mark.c:374
#2  0x4059dc46 in GC_stopped_mark (stop_func=0x4059d528
    at alloc.c:500
#3  0x4059d940 in GC_try_to_collect_inner (
    stop_func=0x4059d528 <GC_never_stop_func>) at alloc.c:353
#4  0x405a7868 in GC_init_inner () at misc.c:703
#5  0x405a3b6d in GC_generic_malloc_inner (lb=100, k=1) at malloc.c:123
#6  0x405a3c9f in GC_generic_malloc (lb=100, k=1) at malloc.c:190
#7  0x405a3f51 in GC_malloc (lb=100) at malloc.c:295
#8  0x4021512b in WinMain () at boehm_crash.c:5
#9  0x402150a5 in __wine_exe_main () at boehm_crash.exe.spec.c:109
#10 0x400b1f5c in start_process () at ../../scheduler/process.c:564
#11 0x400b5ed5 in call_on_thread_stack (func=0x400b1d24)
    at ../../scheduler/sysdeps.c:112

I can't seem to find anything else for now, such as why limits gets too


More information about the wine-devel mailing list