From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14159 invoked by alias); 18 Jan 2006 20:39:38 -0000 Received: (qmail 14151 invoked by uid 22791); 18 Jan 2006 20:39:37 -0000 X-Spam-Check-By: sourceware.org Received: from host217-40-213-68.in-addr.btopenworld.com (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 18 Jan 2006 20:39:36 +0000 Received: from espanola ([192.168.1.110]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jan 2006 20:39:33 +0000 From: "Dave Korn" To: "'Daniel Jacobowitz'" , "'Eric Lemings'" Cc: Subject: RE: Excluding C++ Library Code Date: Wed, 18 Jan 2006 22:24:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <20060118201702.GA13473@nevyn.them.org> Message-ID: 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/msg00175.txt.bz2 Daniel Jacobowitz wrote: > 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'd get the compiler (which already knows about system headers vs. user headers) to pass down the information in a custom DIE myself. But then again, I haven't thought about it in great depth! cheers, DaveK -- Can't think of a witty .sigline today....