From: "Nick Savoiu" <savoiu@ics.uci.edu>
To: <gdb@sources.redhat.com>
Subject: Debugging a large program
Date: Mon, 04 Oct 2004 20:48:00 -0000 [thread overview]
Message-ID: <043c01c4aa53$01e419b0$5a02a8c0@rio> (raw)
Hi,
I'm using GDB to debug a rather large program and I'm running into memory
usage problems that slow down debugging considerably. Just invoking GDB on
the executable (without issuing 'run') results in GDB using up 450MB of
memory.
I think that this is caused by GDB reading in all the symbol info. However,
the code that I'm debugging uses but a small fraction of the code that's
present in the program. Can I somehow tell GDB to only load the symbols it
needs?
Thanks,
Nick
next reply other threads:[~2004-10-04 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 20:48 Nick Savoiu [this message]
2004-10-04 20:54 ` Daniel Jacobowitz
2004-10-05 14:05 ` Andrew Cagney
2004-10-05 14:07 ` Daniel Jacobowitz
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
[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
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='043c01c4aa53$01e419b0$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