Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Nick Savoiu <savoiu@yahoo.com>
Cc: gdb@sourceware.org
Subject: Re: GDB using a lot of CPU time and writing a lot to disk on startup
Date: Wed, 22 Apr 2009 17:57:00 -0000	[thread overview]
Message-ID: <1C89EA31-C5B2-4A7B-B326-5519FF76A318@elis.ugent.be> (raw)
In-Reply-To: <588223.49333.qm@web52003.mail.re2.yahoo.com>


On 22 Apr 2009, at 19:21, Nick Savoiu wrote:

> This is what I get for the whole time that gdb is starting up:
>
> Device:    rrqm/s wrqm/s   r/s   w/s  rsec/s  wsec/s    rkB/s    wkB/ 
> s avgrq-sz avgqu-sz   await  svctm  %util
> sda          0.00 2073.47  0.00 1056.12    0.00 25036.73     0.00  
> 12518.37    23.71     0.94    0.89   0.89  93.67
> sdb          0.00 2073.47  0.00 1056.12    0.00 25036.73     0.00  
> 12518.37    23.71     0.95    0.90   0.89  94.29
>
> There are some reads from time to time but the writes are a constant.
> Is there a way to determine the process that actually does the  
> writing?

You can probably run strace on gdb to verify whether or not it is gdb  
(and if so, where it is writing to). I don't know of a way to check  
this in a system-wide way on Linux though (on Mac OS X, you could use  
fs_usage).


Jonas


  parent reply	other threads:[~2009-04-22 17:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 23:40 Nick Savoiu
2009-04-20 23:48 ` Paul Pluzhnikov
2009-04-20 23:55   ` Daniel Jacobowitz
2009-04-21  0:17     ` Paul Pluzhnikov
2009-04-21  5:22       ` Nick Savoiu
2009-04-21 15:52         ` Mark Kettenis
2009-04-21 19:04           ` Nick Savoiu
2009-04-21 19:52             ` Eli Zaretskii
2009-04-22  6:42               ` Jonas Maebe
2009-04-22 17:23                 ` Nick Savoiu
2009-04-22 17:35                   ` Nick Savoiu
2009-04-22 17:39                     ` Michael Snyder
2009-04-22 17:57                   ` Jonas Maebe [this message]
2009-04-22 19:18                   ` Toby Haynes

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=1C89EA31-C5B2-4A7B-B326-5519FF76A318@elis.ugent.be \
    --to=jonas.maebe@elis.ugent.be \
    --cc=gdb@sourceware.org \
    --cc=savoiu@yahoo.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