In a remote debug session, how do I get to see fresh register values each time I do a 'show all-registers'?
Anmol P. Paralkar
b07584@freescale.com
Mon Apr 2 17:09:00 GMT 2007
On Sun, 1 Apr 2007, Daniel Jacobowitz wrote:
> On Sun, Apr 01, 2007 at 08:16:39PM -0500, Anmol P. Paralkar wrote:
>> Hello,
>
>> I am using GDB 6.6, (ppc64-elf) to remote debug linux running
>> on a PowerPC simulator. I can read the values of the GPR's in
>> the simulator and upon a 'show all-registers', I do see that
>> the registers have values as expected.
>
>> However, on issuing a 'show all-registers' subsequently, I see
>> GDB displaying the resgister values it displayed earlier - not
>> the ones that the simulator now shows. What do I need to do to
>> force GDB to get the fresh set of register values?
>
> What has happened to change the registers? Did the program run, or
> are the registers changing while GDB thinks the simulator is stopped?
>
> In the first case, it's a GDB bug. In the second case, try the
> flushregs command.
flushregs is exactly what I needed. Thank you. (Looking it up also made
me aware of Appendix C: Maintenance commands).
In the first case, please note that I *do* see behaviour as expected.
(Sorry about not being clear, I should perhaps have worded it thus:
"To begin with, I can read the values of the GPR's in the simulator
and upon a 'show all-registers', I do see that the registers have
values as expected. Then, later on, as the program (viz. linux) runs,
and the simulator displays the changed register values, I issue a
'show all-registers' again in GDB, hoping to see the new register
values that the simulator now displays, but GDB continues to display
the old values it displayed). [=> flushregs].
Regards,
Anmol P. Paralkar
More information about the Gdb
mailing list