hans.boehm at hp.com
Tue Aug 28 16:50:55 PDT 2007
Expanding a bit on Alexander's advice, a problem in GC_clear_fl_marks is
normally caused by a corrupted free list. I've seen failures there from
duplicate are premature deallocations, but those tend to result in
infinite loops there. In your case, I'd suspect a write past the end of
an object that corrupted the freelist link in the next object.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Alexander
> Petrossian (PAF)
> Sent: Tuesday, August 28, 2007 1:49 AM
> To: amuseme.lu at yahoo.com.cn
> Cc: gc at napali.hpl.hp.com
> Subject: Re: [Gc] error
> ??> Program received signal SIGBUS, Bus error.
> there is big chapter on debugging things like that
> It proved to be extremely useful.
> You're in ideal situation, the bug is repeatable.
> I belive, you will manage to kill with those hints from Hans.
> In my experience, things like that were _always_ my bugs (or
> bugs in used libraries). It never were a bug in gc (so far ;).
> Alexander Petrossian (PAF), Software Developer, Teligent Russia
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc