This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC/RFA] Per-objfile data mechanism
- From: Mark Kettenis <kettenis at chello dot nl>
- To: carlton at kealia dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sun, 10 Aug 2003 21:03:02 +0200 (CEST)
- Subject: Re: [RFC/RFA] Per-objfile data mechanism
- References: <200307131717.h6DHH425098569@elgar.kettenis.dyndns.org><20030715161729.GA32437@nevyn.them.org> <yf24r1nn3c0.fsf@hawaii.kealia.com>
From: David Carlton <carlton@kealia.com>
Date: Tue, 15 Jul 2003 09:48:31 -0700
On Tue, 15 Jul 2003 12:17:29 -0400, Daniel Jacobowitz
<drow@mvista.com> said:
> The concept is nice, but I share David's concern.
I was also going to write, based on a cursory misreading of Mark's
patch, that it simplified memory management in some circumstances, but
now that I look at it more closely, I think I just misread the patch.
(I may still be misreading the patch; my head is spinning with other
things.) Would it be possible/beneficial to modify the mechanism to
provide an optional per-datum cleanup function as well?
I quite deliberately left per-datum initializers and destructors out
to encourage the use of the per-objfile obstacks. But they can always
be added if they're needed.
So what's the final verdict. Should my patch go in, or do people have
concrete ideas about necessary improvements or alternative
implementations?
Mark