This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Excluding C++ Library Code
- From: Eric Lemings <lemings at roguewave dot com>
- To: 'Daniel Jacobowitz' <drow at false dot org>
- Cc: "'gdb at sources dot redhat dot com'" <gdb at sources dot redhat dot com>, "'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Date: Wed, 18 Jan 2006 13:22:12 -0700
- Subject: RE: Excluding C++ Library Code
> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@false.org]
> Sent: Wednesday, January 18, 2006 1:17 PM
> To: Eric Lemings
> Cc: 'gdb@sources.redhat.com'
> Subject: Re: Excluding C++ Library Code
>
>
> 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?
I figure the responsibility for this would probably reside more
with the compiler than the debugger (e.g. -gnostdinc++) but I
as hoping it could be done already.
Eric.