This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Caching of object/libraries/files
- From: "Nick Savoiu" <savoiu at ics dot uci dot edu>
- To: <gdb at sources dot redhat dot com>
- Date: Thu, 18 Mar 2004 10:46:47 -0800
- Subject: Caching of object/libraries/files
Hi all,
I have a rather large project composed of a small driver executable and
quite a few .so libraries that it uses.
When I invoke it with GDB, upon executing 'run' it takes quite a while for
GDB to do it's thing (i.e. load symbols, whatever else it does) particularly
since it does a lot of disk access.
I was thinking that, if I start a GDB session on this project, run it for a
while then quit and immediately restart a similar session, then most of the
files would be cached. However, I see the same amount of disk access for the
second session when 'run' is invoked as for the first.
Any ideas why this is so? The GDB session itself uses about 340MB and I have
1GB RAM.
Thanks,
Nick