GDB not showing local-to-block variables ?
Iztok Kobal
IKobal@netscape.net
Thu Jan 9 08:01:00 GMT 2003
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
More information about the Gdb
mailing list