Re: Breakpoint when entering of functions on i386

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

> 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