From: Iztok Kobal <IKobal@netscape.net>
To: gdb@sources.redhat.com
Subject: GDB not showing local-to-block variables ?
Date: Wed, 08 Jan 2003 08:09:00 -0000 [thread overview]
Message-ID: <3E1BDC6D.3020604@netscape.net> (raw)
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 ?
next reply other threads:[~2003-01-08 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 8:09 Iztok Kobal [this message]
2003-01-08 9:05 ` Iztok Kobal
2003-01-08 10:16 ` Iztok Kobal
2003-01-08 14:06 ` Elena Zannoni
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=3E1BDC6D.3020604@netscape.net \
--to=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