This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: not debugging low level sources
- From: gnanabaskaran m <gnanabaskar at yahoo dot com>
- To: Daniel Jacobowitz <drow at false dot org>, "Edward S. Peschko" <esp5 at pge dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 16 Feb 2004 04:49:58 -0800 (PST)
- Subject: Re: not debugging low level sources
In hp gdb 3.3, we added a new command "steplast". This
command directly steps into the function, skipping all
the calls(constructors) that evaluates the arguments
Thanks
Gnana
--- Daniel Jacobowitz <drow@false.org> wrote:
> On Fri, Feb 13, 2004 at 06:55:07PM -0800, Edward S.
> Peschko wrote:
> > hey all,
> >
> > I did a google search, and never got a good answer
> to the following question:
> >
> > I want to debug C++ code, and don't want to step
> into stl_alloc.h, etc. I'd rather
> > just step into *user* code - and given the number
> of layers in C++, I'm spending
> > an inordinate amount of time bouncing in and out
> of standard headers.
> >
> > Is there a way to turn off, or otherwise disable,
> what gdb steps into? Something like:
> >
> > (gdb) block <dir>
> >
> > or
> >
> > (gdb) block function
> >
> > or somesuch?
> >
> > Thanks much for any and all answers..
>
> No, there isn't - but I think this is a really great
> idea. Would you
> mind filing it in the GDB bug tracking system (see
> http://sources.redhat.com/gdb/) ?
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian
> GNU/Linux Developer
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html