This is the mail archive of the
mailing list for the GDB project.
MI -var-create frame-addr specification
- From: Christophe LYON <christophe dot lyon at st dot com>
- To: gdb at sourceware dot org
- Date: Fri, 28 Apr 2006 16:45:21 +0200
- Subject: MI -var-create frame-addr specification
Currently, the test gdb.mi/mi-var-display.exp fails with our compiler on
"create variable a2 in different scope".
I am not very familiar with MI, and I don't understand well how the
"frame-addr" parameter works?
Shouldn't a "frame" be represented by a PC,FP pair, instead of only FP?
Indeed, our ABI allows not to allocate space on the stack when entering
a function if it does not need any space. In the testcase, the incr_a()
function is very small, and does not require reserving space on the stack.
Thus, $fp has the same value in incr_a() and in do_special_tests(), so
it's not sufficient to determine the scope of "a" when issuing
"-var-create a2 $fp a".
Is this a limitation of MI? Am I missing something?
Thanks for your feedback,