From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4570 invoked by alias); 18 Jan 2006 20:29:15 -0000 Received: (qmail 4560 invoked by uid 22791); 18 Jan 2006 20:29:14 -0000 X-Spam-Check-By: sourceware.org Received: from Unknown (HELO bco-exchange.bco.roguewave.com) (12.17.213.84) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Jan 2006 20:29:13 +0000 Received: by bco-exchange.bco.roguewave.com with Internet Mail Service (5.5.2657.72) id ; Wed, 18 Jan 2006 13:22:21 -0700 Message-ID: <4FA4B7B3231C5D459E7BAD020213A94203114146@bco-exchange.bco.roguewave.com> From: Eric Lemings To: 'Daniel Jacobowitz' Cc: "'gdb@sources.redhat.com'" , "'gcc@gcc.gnu.org'" Subject: RE: Excluding C++ Library Code Date: Wed, 18 Jan 2006 20:39:00 -0000 MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00174.txt.bz2 > -----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.