This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Breakpoint when entering of functions on i386
- From: Michael Snyder <msnyder at specifix dot com>
- To: yichun wang <wangych at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 26 Nov 2007 10:10:35 -0800
- Subject: Re: Breakpoint when entering of functions on i386
- References: <5f7f5dec0711252308r5825abb8j91d43234ef7b617c@mail.gmail.com> <5f7f5dec0711252310y6c08920cr8464aa2d40ccf05e@mail.gmail.com>
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.