From: "Nick Savoiu" <savoiu@ics.uci.edu>
To: <gdb@sources.redhat.com>
Subject: Re: Debugging a large program
Date: Mon, 04 Oct 2004 23:25:00 -0000 [thread overview]
Message-ID: <04cb01c4aa68$e0a13b00$5a02a8c0@rio> (raw)
In-Reply-To: <20041004221420.GA2937@nevyn.them.org>
----- Original Message -----
From: "Daniel Jacobowitz" <drow@false.org>
To: "Nick Savoiu" <savoiu@ics.uci.edu>; <gdb@sources.redhat.com>
Sent: Monday, October 04, 2004 3:14 PM
Subject: Re: Debugging a large program
> On Mon, Oct 04, 2004 at 05:15:14PM -0400, Daniel Jacobowitz wrote:
> > > BTW, 405MB was for gdb running to main() not just what I said above :)
There
> > > probably are a few global variables but I don't think they should take
up
> > > too much space.
> >
> > That requires loading symbol information for all the shared libraries,
> > which is probably what's taking all the space. 400MB+ is a bit
> > unusual, but I don't know how big your libraries are.
>
> Your libraries contain 288MB of DWARF2 debug information. We're
> winding up with less than twice that in memory usage for reading in
> partial symbols. It probably could be reduced somewhat - say, 30%.
> But some of this data we've just got to hold in memory.
I see. If one of the .so files is not actually used, can I somehow prevent
GDB from loading even its partial symbols? How much memory do partial
symbols use?
Thanks,
Nick
next prev parent reply other threads:[~2004-10-04 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2004-10-05 5:24 ` Daniel Jacobowitz
2004-10-05 15:26 ` Nick Savoiu
[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
-- 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='04cb01c4aa68$e0a13b00$5a02a8c0@rio' \
--to=savoiu@ics.uci.edu \
--cc=gdb@sources.redhat.com \
/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