From: Alexandre Oliva <aoliva@redhat.com>
To: gdb@sources.redhat.com
Subject: any expression to tell whether a variable was optimized out?
Date: Tue, 10 Mar 2009 09:48:00 -0000 [thread overview]
Message-ID: <orskllhfo3.fsf@oliva.athome.lsd.ic.unicamp.br> (raw)
Hi,
I'm working on a debug info quality testsuite for GCC, and I've been
having some trouble telling, in gdb macros, a variable for which no
location expression is available at a certain point in the program (but
for which we do have locations at other points), from one that evaluates
to zero (lifetime constant, or stored in register or memory).
Consider:
(gdb) p x
$1 = <value optimized out>
(gdb) p y
$2 = 0
(gdb) p x == y
1
(gdb) p &x
Can't take address of "x" which isn't an lvalue.
(gdb) p &y
Address requested for identifier "y" which is in register $r12
(gdb) set $temp1 = x
(gdb) set $temp2 = y
(gdb) set z = $temp1 == $temp2
(gdb) p z
1
(gdb) set $temp1 = x + 1
(gdb) set $temp2 = y + 1
(gdb) set z = $temp1 == $temp2
(gdb) p z
1
Is there really no way to set a gdb variable to something equivalent to
the boolean result of valprint.c:value_optimized_out()? Any reason for
that, other than that nobody needed it before?
Thanks in advance,
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
next reply other threads:[~2009-03-10 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 9:48 Alexandre Oliva [this message]
2009-03-10 12:59 ` Daniel Jacobowitz
2009-03-10 15:48 ` Thiago Jung Bauermann
2009-03-10 16:45 ` Alexandre Oliva
2009-03-10 18:45 ` Thiago Jung Bauermann
2009-03-10 18:48 ` Thiago Jung Bauermann
2009-03-17 21:07 ` Tom Tromey
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=orskllhfo3.fsf@oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--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