QEMU: Difference between revisions
→Usage: getting DEBUG output
| [unchecked revision] | [unchecked revision] |
m (→GDB-stub) |
(→Usage: getting DEBUG output) |
||
Line 125:
will load into GDB your kernel and then connect to QEMU. Be sure to compile your kernel with the GCC option <tt>-g</tt> for debugging symbols. Now you may debug your kernel as a C program.
If you have an SMP kernel, check out the <tt>info threads</tt> and <tt>thread</tt> commands. Note: as far as I know you cannot examine control registers or physical memory through GDB. So the QEMU monitor is the only way to go for that information.
===Getting detailed logs===
Most of the QEMU source code has commented lines of the form:
// #define DEBUG_*
If you are willing to edit and recompile QEMU then you can get a good deal of debugging info output to stdout by doing so.
==See Also==
| |||