This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Excluding C++ Library Code

From: Mike Stump <mrs at apple dot com>
To: Eric Lemings <lemings at roguewave dot com>
Cc: "'Daniel Jacobowitz'" <drow at false dot org>, "'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 19:25:58 -0800
Subject: Re: Excluding C++ Library Code
References: <4FA4B7B3231C5D459E7BAD020213A94203114146@bco-exchange.bco.roguewave.com>

On Jan 18, 2006, at 12:22 PM, Eric Lemings wrote:

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.

Either, we can mark the debug information with `system header', or gdb can strncmp ("/usr/include") and a few others... :-) gcc has a slightly easier time know when a header is a system header, but a project GUI has a easier time having check boxes for components you want to stop in and which ones you don't want to stop in, with system headers being just one of the boxes.

Follow-Ups:
- Re: Excluding C++ Library Code
  - From: 'Daniel Jacobowitz'

References:
- RE: Excluding C++ Library Code
  - From: Eric Lemings

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]