Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Iztok Kobal <IKobal@netscape.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB not showing local-to-block variables ?
Date: Wed, 08 Jan 2003 14:06:00 -0000	[thread overview]
Message-ID: <15900.12642.213680.805002@localhost.redhat.com> (raw)
In-Reply-To: <3E1BDC6D.3020604@netscape.net>

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


  parent reply	other threads:[~2003-01-08 14:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08  8:09 Iztok Kobal
2003-01-08  9:05 ` Iztok Kobal
2003-01-08 10:16 ` Iztok Kobal
2003-01-08 14:06 ` Elena Zannoni [this message]
2003-01-09  8:01   ` Iztok Kobal
2003-01-09  8:27 ` Iztok Kobal
2003-01-09  8:55   ` Iztok Kobal
2003-01-09  9:53     ` Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15900.12642.213680.805002@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=IKobal@netscape.net \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox