Re: [Qemu-devel] Dump registers?

[malc]

On Sun, 22 Feb 2009, Pierre-Alexandre Meyer wrote:

> Good morning,
> 
>   I am developing an application at the bootloader level that
> eventually jumps into protected mode. My testing is done using the
> qemu Ubuntu Intrepid build (0.9.1).
> 
> Doing something like
> 
>   qemu -M pc -hda foo.vmdk -m 1000 -no-kqemu -boot c -S -s
> 
> and connecting gdb works great... until the application jumps into
> protected mode when gdb becomes really confused.
> 
> Setting a break point at the first function after protected mode doesn't
> work.
> 
> With no break points, if I SIGINT the program after the jump, gdb is confused:
> 
>    Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 
> This makes sense I suppose since the segment registers were changed
> since gdb was started. I have then access to the registers but I am not sure
> how accurate they are.
> 
> Is there a way to ask qemu to dump these registers (as well as the
> descriptor tables)? I saw once a dump like:
> 

Switch to QEMU monitor and type `info registers'.

[..snip..]

> 
> This is exactly what I am looking for. Any idea if I can force such a
> dump on demand and/or fix gdb?
> 
> Thank you.
> 
> (Please CC: me when replying, since I am not on the list)
> 
> 

-- 
mailto:address@hidden