From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: MI: performance of getting stack arguments
Date: Wed, 26 Apr 2006 14:59:00 -0000 [thread overview]
Message-ID: <20060426141002.GB20166@nevyn.them.org> (raw)
In-Reply-To: <e2nup3$1t7$1@sea.gmane.org>
On Wed, Apr 26, 2006 at 06:06:26PM +0400, Vladimir Prus wrote:
> Ok, I'll try to do this. First on -stack-list-arguments, since it's pretty
> slow to. But, maybe I should be using callgrind (part of valgrind suite)
> for profiling?
I've had a lot of trouble getting the valgrind tools to play nice with
GDB; they want to debug the children too and get confused by ptrace.
But it looks like there've been some changes and now the default is not
to do that, so maybe it'll work better.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-26 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 16:40 Vladimir Prus
2006-04-18 16:45 ` Daniel Jacobowitz
2006-04-18 21:15 ` Jim Ingham
2006-04-19 7:55 ` Vladimir Prus
2006-04-19 16:13 ` Eli Zaretskii
2006-04-20 8:50 ` Daniel Jacobowitz
2006-04-26 14:10 ` Vladimir Prus
2006-04-26 14:59 ` Daniel Jacobowitz [this message]
2006-04-26 18:02 ` Vladimir Prus
2006-04-26 18:17 ` Daniel Jacobowitz
2006-04-18 19:11 ` Jim Ingham
2006-04-18 21:35 ` Robert Dewar
2006-04-18 21:37 ` Jim Ingham
2006-04-19 6:08 ` Robert Dewar
2006-04-19 7:30 ` Vladimir Prus
2006-04-19 6:11 ` Nick Roberts
2006-04-19 8:45 ` Eli Zaretskii
2006-04-19 9:02 ` Nick Roberts
2006-04-19 12:40 ` Eli Zaretskii
2006-04-20 10:22 ` Jim Ingham
2006-04-19 6:20 ` Vladimir Prus
2006-04-19 8:28 ` Eli Zaretskii
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=20060426141002.GB20166@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.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