From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JukJV-0004T4-C5 for qemu-devel@nongnu.org; Sat, 10 May 2008 04:20:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JukJT-0004Sg-35 for qemu-devel@nongnu.org; Sat, 10 May 2008 04:20:15 -0400 Received: from [199.232.76.173] (port=51456 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JukJS-0004Sd-Rc for qemu-devel@nongnu.org; Sat, 10 May 2008 04:20:14 -0400 Received: from tapir.sajinet.com.pe ([66.139.79.212]:33294) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JukJS-00064t-Fa for qemu-devel@nongnu.org; Sat, 10 May 2008 04:20:14 -0400 Date: Sat, 10 May 2008 03:40:05 -0500 From: Carlo Marcelo Arenas Belon Message-ID: <20080510084005.GA28397@tapir> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline Subject: [Qemu-devel] [PATCH] documentation: use table to document advanced GDB commands Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --- --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="qemu-doc-gdb.patch" 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 --6c2NcOVqGQ03X4Wi--