Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Nick Savoiu" <savoiu@ics.uci.edu>
To: <gdb@sources.redhat.com>
Subject: Caching of object/libraries/files
Date: Thu, 18 Mar 2004 18:47:00 -0000	[thread overview]
Message-ID: <04b201c40d19$602c8390$a60bc380@ics.uci.edu> (raw)

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


             reply	other threads:[~2004-03-18 18:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18 18:47 Nick Savoiu [this message]
2004-03-18 19:34 ` Daniel Jacobowitz
2004-03-18 19:52   ` Nick Savoiu
2004-03-24 23:11 Nick Savoiu

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='04b201c40d19$602c8390$a60bc380@ics.uci.edu' \
    --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