From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1661 invoked by alias); 9 Jan 2003 08:01:32 -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 1246 invoked from network); 9 Jan 2003 08:01:29 -0000 Received: from unknown (HELO gateway.sysen) (212.118.92.51) by 209.249.29.67 with SMTP; 9 Jan 2003 08:01:29 -0000 Received: from netscape.net (zv-23.sysen [10.0.30.23]) by gateway.sysen (8.9.3/8.9.3/12.06.1999) with ESMTP id JAA08467; Thu, 9 Jan 2003 09:01:11 +0100 Message-ID: <3E1D2C5C.8010005@netscape.net> Date: Thu, 09 Jan 2003 08:01:00 -0000 From: Iztok Kobal User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020903 X-Accept-Language: sl, en-us MIME-Version: 1.0 To: Elena Zannoni CC: gdb@sources.redhat.com Subject: Re: GDB not showing local-to-block variables ? References: <3E1BDC6D.3020604@netscape.net> <15900.12642.213680.805002@localhost.redhat.com> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-01/txt/msg00119.txt.bz2 Elena Zannoni wrote: >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. > > Jesus ! And only one answer posted on known thing ? Thank you, Elena ! So what to do in my case now ? I have projects reverted from gcc-2.95 and old automake/autoconf because I have believed that gcc-3.2/gdb-5.2.x is better combination ! 1. Revert to use of the gcc-2.95/gdb3/4 or what ? 2. Put all kinds of outputs throughout the tons of the shared libs to make the debugging stoneage way ? 3. Or somebody (maybe A.Cagney) will appoint me to the right solution - I really doubt that there is no one ! Is this behaviour also the case with the gdb-5.3 ? I have tried to compile it with my gcc-3.2 and it requests the libterm library which I do not have in my SuSE 8.1 distro. I will not even try again if this mess with the debugging info is the same in gdb-5.3 ! I. >Elena > >. > > > -- Iztok Kobal Iskra SISTEMI, d.d. Stegne 21 1000 Ljubljana Tel.: +386 (0)1 5004368 Fax.: +386 (0)1 5111283 E-mail: iztok.kobal@iskrasistemi.si WWW: www.iskrasistemi.si