From: Michael Snyder <msnyder@vmware.com>
To: Nick Savoiu <savoiu@yahoo.com>
Cc: "gdb@sourceware.org" <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:39:00 -0000 [thread overview]
Message-ID: <49EF53D9.9050209@vmware.com> (raw)
In-Reply-To: <923173.50385.qm@web52006.mail.re2.yahoo.com>
Nick Savoiu wrote:
> Forgot to mention, the 'swap used' does not change during this time so it's highly unlikely that swapping is the issue. Given the write rate even if swapping was happening it should not take more than a few seconds.
Forgive me if this has already been asked, but...
is there any chance that you have a stray .gdbinit file
with some odd command in it, such as "maint print symbols"?
next prev parent reply other threads:[~2009-04-22 17:35 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 [this message]
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=49EF53D9.9050209@vmware.com \
--to=msnyder@vmware.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