From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18522 invoked by alias); 8 Jan 2003 14:06:42 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18490 invoked from network); 8 Jan 2003 14:06:37 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by 209.249.29.67 with SMTP; 8 Jan 2003 14:06:37 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h08DciB28456 for ; Wed, 8 Jan 2003 08:38:44 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h08E6Pa07461 for ; Wed, 8 Jan 2003 09:06:25 -0500 Received: from localhost.redhat.com (romulus-int.sfbay.redhat.com [172.16.27.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h08E6Pn10703 for ; Wed, 8 Jan 2003 09:06:25 -0500 Received: by localhost.redhat.com (Postfix, from userid 469) id 9CE51FF79; Wed, 8 Jan 2003 09:10:44 -0500 (EST) From: Elena Zannoni MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15900.12642.213680.805002@localhost.redhat.com> Date: Wed, 08 Jan 2003 14:06:00 -0000 To: Iztok Kobal Cc: gdb@sources.redhat.com Subject: Re: GDB not showing local-to-block variables ? In-Reply-To: <3E1BDC6D.3020604@netscape.net> References: <3E1BDC6D.3020604@netscape.net> X-SW-Source: 2003-01/txt/msg00077.txt.bz2 Iztok Kobal writes: > System: i686, SuSE 8.1, kernel 2.4.19, gcc-3.2, gdb-5.2.1 > > code is configured to use exceptions and compiled using the > --enable-debug. When invoking the gdb, it does not show the variables > which are local to the block within some function: > > void function (some argument) { > try { > some variable; // which is not displayed by the debugger > ..... > ...... > } > catch (...) { > .... > } > } > > When trying to display this variable as it was the watch variable, the > debugger reports that there is no such symbol in the current stack frame. > > Is this the debugger problem or there is an option to be used at compile > time to get this info ? > I think this is the same problem as the one in http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=833 and it is due to gdb not understanding dwarf2 debug info that is stored in .debug_ranges sections. Elena