[Qemu-devel] [PATCH] documentation: use table to document advanced GDB commands

[Qemu-devel] [PATCH] documentation: use table to document advanced GDB commands

[Carlo Marcelo Arenas Belon]

[-- Attachment #1: Type: text/plain, Size: 200 bytes --]

The attached patch corrects a formatting issue in qemu-doc.texi from r4391 and
shown by :

  texi2html -monolithic -number qemu-doc.texi
  ** Unknown command `@code' (left as is) (l. 1954)

Carlo
---

[-- Attachment #2: qemu-doc-gdb.patch --]
[-- Type: text/plain, Size: 1241 bytes --]

Index: qemu-doc.texi
===================================================================
--- qemu-doc.texi	(revision 4402)
+++ qemu-doc.texi	(working copy)
@@ -1951,7 +1951,7 @@
 Advanced debugging options:
 
 The default single stepping behavior is step with the IRQs and timer service routines off.  It is set this way because when gdb executes a single step it expects to advance beyond the current instruction.  With the IRQs and and timer service routines on, a single step might jump into the one of the interrupt or exception vectors instead of executing the current instruction. This means you may hit the same breakpoint a number of times before executing the instruction gdb wants to have executed.  Because there are rare circumstances where you want to single step into an interrupt vector the behavior can be controlled from GDB.  There are three commands you can query and set the single step behavior:
-@enumerate @code
+@table @code
 @item maintenance packet qqemu.sstepbits
 
 This will display the MASK bits used to control the single stepping IE:
@@ -1976,7 +1976,7 @@
 sending: "qemu.sstep=0x5"
 received: "OK"
 @end example
-@end enumerate
+@end table
 
 @node pcsys_os_specific
 @section Target OS specific information