qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4417] Correct a formatting issue (Carlo Marcelo Arenas Belon).
Date: Sat, 10 May 2008 19:37:45 +0000	[thread overview]
Message-ID: <E1Juut7-00040k-Sy@cvs.savannah.gnu.org> (raw)

Revision: 4417
          http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4417
Author:   edgar_igl
Date:     2008-05-10 19:37:44 +0000 (Sat, 10 May 2008)

Log Message:
-----------
Correct a formatting issue (Carlo Marcelo Arenas Belon).

Modified Paths:
--------------
    trunk/qemu-doc.texi

Modified: trunk/qemu-doc.texi
===================================================================
--- trunk/qemu-doc.texi	2008-05-10 19:20:33 UTC (rev 4416)
+++ trunk/qemu-doc.texi	2008-05-10 19:37:44 UTC (rev 4417)
@@ -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

                 reply	other threads:[~2008-05-10 19:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1Juut7-00040k-Sy@cvs.savannah.gnu.org \
    --to=edgar.iglesias@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).