[Gc] Re: Re: Re: FW: Re: Cannot print call chain
hans.boehm at hp.com
Wed Jul 14 11:33:07 PDT 2010
It would also be good to verify that p and GC_base(p) are the same.
This test checks that the allocated object is big enough to hold the debug information. The fact that it doesn't appear to be suggests that either there's something seriously inconsistent here, or something has gone seriously wrong when the object was allocated.
> -----Original Message-----
> From: gc-bounces at linux.hpl.hp.com [mailto:gc-bounces at linux.hpl.hp.com]
> On Behalf Of Ivan Maidanski
> Sent: Wednesday, July 14, 2010 5:36 AM
> To: biosli
> Cc: gc at linux.hpl.hp.com
> Subject: Re: [Gc] Re: Re: Re: FW: Re: Can not print call chain
> Wed, 14 Jul 2010 11:43:03 +0000 (UTC) biosli <biosli at hotmail.com>:
> > Hi, Ivan:
> > Ivan Maidanski <ivmai at ...> writes:
> > > > GC_debug_print_heap_obj_proc calls GC_HAS_DEBUG_INFO(p), and
> return false
> > > > because (sz < DEBUG_BYTES + EXTRA_BYTES).
> And what are that values (sz, DEBUG_BYTES, EXTRA_BYTES) when (sz <
> DEBUG_BYTES + EXTRA_BYTES)?
> > >
> > > Hmm... sz=GC_size(obj) which should be >= DEBUG_BYTES + EXTRA_BYTES
> if obj
> > was allocated by GC_debug_...
> > > You do all your allocationa thru GC_debug_ (or GC_MALLOC... with
> > on), right?
> > >
> > Thanks your help and the patience.
> > Yes, all melloc and free call thru GC_debug_(such as malloc, free)
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc