This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Debugging a large program
- From: Daniel Jacobowitz <drow at false dot org>
- To: Nick Savoiu <savoiu at ics dot uci dot edu>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 4 Oct 2004 16:49:42 -0400
- Subject: Re: Debugging a large program
- References: <043c01c4aa53$01e419b0$5a02a8c0@rio>
On Mon, Oct 04, 2004 at 01:44:55PM -0700, Nick Savoiu wrote:
> 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?
GDB already reads in only what it needs, and more lazily - however,
there's some information about every symbol that's needed. 450MB is
pretty remarkable; how big is the application? readelf -S output would
be the best way to answer the question.
--
Daniel Jacobowitz