From: gnanabaskaran m <gnanabaskar@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>, "Edward S. Peschko" <esp5@pge.com>
Cc: gdb@sources.redhat.com
Subject: Re: not debugging low level sources
Date: Mon, 16 Feb 2004 12:50:00 -0000 [thread overview]
Message-ID: <20040216124958.13792.qmail@web40912.mail.yahoo.com> (raw)
In-Reply-To: <20040216032250.GA2685@nevyn.them.org>
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
prev parent reply other threads:[~2004-02-16 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 2:58 Edward S. Peschko
2004-02-16 3:22 ` Daniel Jacobowitz
2004-02-16 12:50 ` gnanabaskaran m [this message]
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=20040216124958.13792.qmail@web40912.mail.yahoo.com \
--to=gnanabaskar@yahoo.com \
--cc=drow@false.org \
--cc=esp5@pge.com \
--cc=gdb@sources.redhat.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