From: Daniel Jacobowitz <drow@false.org>
To: Eric Lemings <lemings@roguewave.com>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: Excluding C++ Library Code
Date: Wed, 18 Jan 2006 20:18:00 -0000 [thread overview]
Message-ID: <20060118201702.GA13473@nevyn.them.org> (raw)
In-Reply-To: <4FA4B7B3231C5D459E7BAD020213A94203114145@bco-exchange.bco.roguewave.com>
On Wed, Jan 18, 2006 at 01:08:55PM -0700, Eric Lemings wrote:
> Greetings,
>
> This should probably be listed in a FAQ somewhere but here goes. How do
> I prevent GDB from stepping through/stopping in code (template functions,
> inline functions, etc.) contained in standard C++ library header files?
GDB doesn't support this, unfortunately.
Right now the infrastructure for it isn't there, but someday it will
be. But how would you indicate to the debugger what constituted
"uninteresting" headers?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-01-18 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 20:17 Eric Lemings
2006-01-18 20:18 ` Daniel Jacobowitz [this message]
2006-01-18 22:24 ` Dave Korn
2006-01-18 20:39 Eric Lemings
2006-01-19 3:54 ` Mike Stump
2006-01-19 4:31 ` 'Daniel Jacobowitz'
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=20060118201702.GA13473@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=lemings@roguewave.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