public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/24417] reverse execution part of the manual is written backwards
Date: Tue, 13 Dec 2022 10:12:04 +0000	[thread overview]
Message-ID: <bug-24417-4717-eZE21ZXszn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24417-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24417

B. Larsen <blarsen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |blarsen at redhat dot com

--- Comment #2 from B. Larsen <blarsen at redhat dot com> ---
I just checked the GDB documentation and found the following paragraph on the
page that introduces reverse debugging:

On some platforms, gdb has built-in support for reverse execution, activated
with the
record or record btrace commands. See Chapter 7 [Process Record and Replay],
page 101.
Some remote targets, typically full system emulators, support reverse execution
directly
without requiring any special command.

It is the 4th paragraph and comes before the explanation of commands. Is this
issue fixed already, or would you still like improvements?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

           reply	other threads:[~2022-12-13 10:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-24417-4717@http.sourceware.org/bugzilla/>]

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=bug-24417-4717-eZE21ZXszn@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).