[Gc] Difference between version 6.3 and latest which is 6.4
hans.boehm at hp.com
Tue Jun 21 12:06:11 PDT 2005
The collector generally has trouble finding thread-specific data.
Does Windows have a way to enumerate it? In general it seems to
be very hard to find it, since it's very dependent on the specific
threads implementation. (I wouldn't be opposed to platform-specific
patches to trace from thread-specific data, provided they do no
harm if you are running the "wrong" version of the threads
The standard work-around is to also store a copy of the pointer in
some static data structure, or to allocate it with
> -----Original Message-----
> From: Emmanuel Stapf [ES] [mailto:manus at eiffel.com]
> Sent: Tuesday, June 21, 2005 11:36 AM
> To: manus at eiffel.com; Boehm, Hans
> Cc: gc at napali.hpl.hp.com
> Subject: RE: [Gc] Difference between version 6.3 and latest
> which is 6.4
> So I was using `malloc' for some C structures that actually
> had some references to objects I wanted to maintain alive. So
> my bad. I removed those occurences to use `GC_malloc' instead.
> It did go further, but it still fails. It is collecting a
> piece of memory that is directly referenced in the per thread
> data of a thread. Could it be that the gc does not know about
> those per thread data location?
> > -----Original Message-----
> > From: gc-bounces at napali.hpl.hp.com
> > [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Emmanuel
> Stapf [ES]
> > Sent: Tuesday, June 21, 2005 7:56 AM
> > To: 'Hans Boehm'
> > Cc: gc at napali.hpl.hp.com
> > Subject: RE: [Gc] Difference between version 6.3 and latest
> > which is 6.4
> > > Do the malloc'ed objects contain pointers to the garbage-collected
> > > heap?
> > As far as I know they don't. But I'll double check this morning.
> > Regards,
> > Manu
> > _______________________________________________
> > Gc mailing list
> > Gc at linux.hpl.hp.com
> > https://www.hpl.hp.com/hosted/linux/mail-archives/gc/
More information about the Gc