This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
any expression to tell whether a variable was optimized out?
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Tue, 10 Mar 2009 06:48:28 -0300
- Subject: any expression to tell whether a variable was optimized out?
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