From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Per-objfile data mechanism
Date: Tue, 15 Jul 2003 16:17:00 -0000 [thread overview]
Message-ID: <20030715161729.GA32437@nevyn.them.org> (raw)
In-Reply-To: <200307131717.h6DHH425098569@elgar.kettenis.dyndns.org>
On Sun, Jul 13, 2003 at 07:17:04PM +0200, Mark Kettenis wrote:
> This patch adds a per-objfile data mechanism to GDB, and uses that to
> store DWARF2 frame info instead of abusing objfile->sym_private. The
> latter could lead to problems on certain platforms according to
> Daniel.
Cygwin appears to be affected by this, so we should definitely reach
some conclusion before 6.0.
> Comments? OK to check this in? Do we want this on the release branch
> too?
The concept is nice, but I share David's concern. The way you
implemented this, every objfile always pays the cost of the extra
storage; there's an abstraction benefit, but a memory and simplicity
penalty. I could go either way.
We should reach a decision one way or the other, though. I needed a
new per-objfile datum just yesterday.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-15 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 17:17 Mark Kettenis
2003-07-15 15:55 ` David Carlton
2003-07-15 16:17 ` Daniel Jacobowitz [this message]
2003-07-15 16:48 ` David Carlton
2003-07-15 17:27 ` Daniel Jacobowitz
2003-08-10 19:03 ` Mark Kettenis
2003-08-11 15:45 ` David Carlton
2003-08-12 20:08 ` Andrew Cagney
2003-08-12 20:51 ` David Carlton
2003-08-21 22:42 ` Mark Kettenis
2003-09-07 4:26 ` Daniel Jacobowitz
2003-08-13 20:54 ` Daniel Jacobowitz
2003-07-15 17:14 ` Andrew Cagney
2003-07-15 20:00 ` Elena Zannoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030715161729.GA32437@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox