From: Daniel Jacobowitz <drow@false.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb@sourceware.org, jzhang918@gmail.com
Subject: Re: slow script execution when debugging large binaries
Date: Thu, 10 Aug 2006 20:40:00 -0000 [thread overview]
Message-ID: <20060810204027.GA32182@nevyn.them.org> (raw)
In-Reply-To: <200608101633.08373.vapier@gentoo.org>
On Thu, Aug 10, 2006 at 04:33:07PM -0400, Mike Frysinger wrote:
> i'm playing with kgdb and in the process have been learning/writing up little
> code snippets to make debugging easier ... for example, a small function that
> will dump the dmesg buffer in kgdb ... now, the issue at hand isnt kgdb :)
Could you build a GDB which includes profiling data (I think it's
--enable-profile, check gdb/configure.ac) and then use
maint set profile to generate a profile data file for this?
It'll tell you where the problem is - probably something is doing
unnecessary symbol lookup.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-10 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 20:32 Mike Frysinger
2006-08-10 20:40 ` Daniel Jacobowitz [this message]
2006-08-10 21:48 ` Mike Frysinger
2006-08-10 21:55 ` Daniel Jacobowitz
2006-08-10 22:04 ` Mike Frysinger
2006-08-10 22:05 ` Daniel Jacobowitz
2006-08-10 22:21 ` Mike Frysinger
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=20060810204027.GA32182@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jzhang918@gmail.com \
--cc=vapier@gentoo.org \
/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