From: "yichun wang" <wangych@gmail.com>
To: "Joel Brobecker" <brobecker@adacore.com>
Cc: "Michael Snyder" <msnyder@specifix.com>, gdb@sourceware.org
Subject: Re: Breakpoint when entering of functions on i386
Date: Tue, 27 Nov 2007 07:53:00 -0000 [thread overview]
Message-ID: <5f7f5dec0711262353i6f73c081hf100f61cd020b5c4@mail.gmail.com> (raw)
In-Reply-To: <20071127072541.GJ3670@adacore.com>
GDB is easy to interact and control, for example, one feature of my
script is to start print calling graph after hit some function (just a
breakpoint), or to print the value of arguments. It can simply give
you many controls of program, for source level to assembly level, with
little programming job.
Other tools could be also possible, for example, a plugin to
valgrind/callgrind will also work, but it may require more knowledge
and programming. Currently I'm using perl+gdb, except performance, the
script works just fine.
-Yichun.
On Nov 27, 2007 3:25 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> > Thanks Michael, to define an "interesting subset" should improve the
> > performance , but I need generate call graph for many different
> > applications, and this script won't have any knowledge of the
> > application, so this might not work...
>
> Is there a reason why you have to use GDB instead of a more specialized
> tool?
>
> --
> Joel
>
next prev parent reply other threads:[~2007-11-27 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5f7f5dec0711252308r5825abb8j91d43234ef7b617c@mail.gmail.com>
2007-11-26 7:10 ` yichun wang
2007-11-26 18:23 ` Michael Snyder
2007-11-27 5:52 ` yichun wang
2007-11-27 7:25 ` Joel Brobecker
2007-11-27 7:53 ` yichun wang [this message]
2007-11-27 20:51 ` Michael Snyder
2007-11-27 21:04 ` Joel Brobecker
2007-11-28 0:42 ` Michael Snyder
2007-11-28 0:46 ` Joel Brobecker
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=5f7f5dec0711262353i6f73c081hf100f61cd020b5c4@mail.gmail.com \
--to=wangych@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=msnyder@specifix.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