Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "yichun wang" <wangych@gmail.com>
To: "Michael Snyder" <msnyder@specifix.com>
Cc: gdb@sourceware.org
Subject: Re: Breakpoint when entering of functions on i386
Date: Tue, 27 Nov 2007 05:52:00 -0000	[thread overview]
Message-ID: <5f7f5dec0711262152n56165a36q9f9d949bf829b537@mail.gmail.com> (raw)
In-Reply-To: <1196100635.2501.12.camel@localhost.localdomain>

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...

Thanks,
-Yichun.

On Nov 27, 2007 2:10 AM, Michael Snyder <msnyder@specifix.com> wrote:
>
> On Mon, 2007-11-26 at 15:10 +0800, yichun wang wrote:
> > Hi,
> >
> > I'm now working on a script which will print calling graph by stepping
> > through program with GDB. The script actually works fine in some small
> > cases, but one big performance bottleneck is that I used "watch $ebp"
> > to catch the happening of function call, and it will become really
> > slow when in some cases, local variable/arguments are heavily used. So
> > my question is:
> >
> >     Is there any better way in GDB to capture function call event?
>
> What about just setting breakpoints on all functions?
>
> That way, if there is a way to define an "interesting subset"
> of functions, you can limit your breakpoints to that subset,
> and save a lot of time.
>
>
>
>


  reply	other threads:[~2007-11-27  5:52 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 [this message]
2007-11-27  7:25       ` Joel Brobecker
2007-11-27  7:53         ` yichun wang
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=5f7f5dec0711262152n56165a36q9f9d949bf829b537@mail.gmail.com \
    --to=wangych@gmail.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