how to examine data with compiler optimization option set?
Paul Koning
Paul_Koning@dell.com
Thu Sep 4 14:15:00 GMT 2008
>>>>> "Robert" == Robert Dewar <dewar@adacore.com> writes:
Robert> Paul Koning wrote:
>> Is the problem inadequate debug information (i.e., the values are
>> there, but there isn't debug data that points to the correct
>> registers or stack slots) -- or is the problem that the values you
>> want to see are dead by the time you get to them and the registers
>> holding them have been reused by then? Or something in between,
>> i.e., the values are technically dead, but the registers have NOT
>> yet been reused so the debug information can (and should) still
>> show where they are.
Robert> Well on entry to a function, (if you breakpoint on entry),
Robert> the parameters cannot have been overwritten yet I would
Robert> think!
Agreed.
I haven't run into trouble there (on MIPS that is), provided the
breakpoint is set after the function prologue.
paul
More information about the Gdb
mailing list