From: Andrew Cagney <cagney@gnu.org>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: Daniel Jacobowitz <drow@false.org>,
Nick Savoiu <savoiu@ics.uci.edu>,
gdb@sources.redhat.com
Subject: Re: Debugging a large program
Date: Mon, 11 Oct 2004 13:59:00 -0000 [thread overview]
Message-ID: <4169E90C.10803@gnu.org> (raw)
In-Reply-To: <20041008121611.A90098@molenda.com>
>> Doing this means abandoning the psymtab and instead having symbol code
>> directly read each symbol or address as it is needed, and with the
>> minimum auxulary information (i.e., direct from disk).
> For what it's worth, we've been working on a less ambitious scheme
> at Apple for the past month, with similar benefits.
(dejavu, sigh)
> Andrew's approach is much cooler, but it's definitely not something
> that could be done with stabs (as it exists today), and we're stuck
> on stabs on MacOS X for a while still.
>
> Anyway, just a point of information. It was a HUGE win for us on
> extremely large applications where they have many large solibs and
> the developer is only debugging code in a couple of them.
The existing symfile code can be pushed down a level, hiding it behind a
new symtab proxy.
Andrew
next prev parent reply other threads:[~2004-10-11 2:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F51E79B1-195C-11D9-ACAD-000A9569836A@gnu.org>
2004-10-08 21:35 ` Jason Molenda
2004-10-11 1:46 ` Daniel Berlin
2004-10-11 6:10 ` Andrew Cagney
2004-10-11 13:59 ` Andrew Cagney [this message]
2004-10-04 21:15 Nick Savoiu
2004-10-04 21:16 ` Daniel Jacobowitz
2004-10-04 23:21 ` Daniel Jacobowitz
2004-10-04 23:25 ` Nick Savoiu
2004-10-05 5:24 ` Daniel Jacobowitz
2004-10-05 15:26 ` Nick Savoiu
-- strict thread matches above, loose matches on Subject: below --
2004-10-04 20:48 Nick Savoiu
2004-10-04 20:54 ` Daniel Jacobowitz
2004-10-05 14:05 ` Andrew Cagney
2004-10-05 14:07 ` Daniel Jacobowitz
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=4169E90C.10803@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=jason-swarelist@molenda.com \
--cc=savoiu@ics.uci.edu \
/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