Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>,
	Nick Savoiu <savoiu@yahoo.com>,
	        gdb@sourceware.org
Subject: Re: GDB using a lot of CPU time and writing a lot to disk on startup
Date: Tue, 21 Apr 2009 00:17:00 -0000	[thread overview]
Message-ID: <8ac60eac0904201654h1775560se59718b127ccbfad@mail.gmail.com> (raw)
In-Reply-To: <20090420234805.GA28850@caradoc.them.org>

On Mon, Apr 20, 2009 at 4:48 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Mon, Apr 20, 2009 at 04:39:56PM -0700, Paul Pluzhnikov wrote:
>> > I used pstack every second until the debugging actually starts and here
>> > are all the unique #0 locations in the pstack output.
...
>> This output is bogus.
>
> I thought that too the first time I read it - but see his description
> of the output (above) again :-)

Oops. I see it now; thanks.

So most of the time (481 of 461) GDB is blocked in stat. Not a big surprize.

> Nick, it sounds to me like you're debugging something that you haven't
> got enough RAM for - is the disk I/O your swap space?

I don't (yet) see any evidence for swapping either. Do you?

Cheers,
-- 
Paul Pluzhnikov


  reply	other threads:[~2009-04-20 23:55 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 [this message]
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
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=8ac60eac0904201654h1775560se59718b127ccbfad@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --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