From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1644 invoked by alias); 11 Mar 2008 00:33:02 -0000 Received: (qmail 1600 invoked by uid 22791); 11 Mar 2008 00:33:00 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 11 Mar 2008 00:32:41 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 185D9983B5; Tue, 11 Mar 2008 00:32:39 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id ED5A29801D; Tue, 11 Mar 2008 00:32:38 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JYsQ2-0003tR-79; Mon, 10 Mar 2008 20:32:38 -0400 Date: Tue, 11 Mar 2008 00:37:00 -0000 From: Daniel Jacobowitz To: Brian Budge Cc: gdb@sourceware.org Subject: Re: breakpoints and symbol examination problems Message-ID: <20080311003238.GA14908@caradoc.them.org> Mail-Followup-To: Brian Budge , gdb@sourceware.org References: <5b7094580803101705m7bc6e8ffqa480a74d9b0ab548@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5b7094580803101705m7bc6e8ffqa480a74d9b0ab548@mail.gmail.com> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00113.txt.bz2 On Mon, Mar 10, 2008 at 05:05:17PM -0700, Brian Budge wrote: > Hi all - > > I'm having an issue with reaching breakpoints and examining symbols in > my C++ code via gdb. I can set breakpoints in my .cpp files and > actually reach these, but if I put breakpoints in included header > files (in template code), my program will run right through the > breakpoints. Try a snapshot of the current CVS HEAD or the 6.8 branch. This should be fixed. > Additionally, I can't seem to examine any "stack" variables once in > these template functions. I can see member variables, global > variables, and function parameters. This may be fixed, or it may be a compiler bug. GCC is not very good about emitting local variable information in optimized code. -- Daniel Jacobowitz CodeSourcery