From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/doc: extend the documentation of the jump command
Date: Mon, 24 Apr 2023 19:30:53 +0300 [thread overview]
Message-ID: <831qk9xmwy.fsf@gnu.org> (raw)
In-Reply-To: <4da5caec8b9bba91ffc25349e86bc99797f4c9e2.1682352919.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Mon, 24 Apr 2023 17:15:38 +0100)
> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Mon, 24 Apr 2023 17:15:38 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>
> This commit addresses PR gdb/7946. While checking for bugs relating
> to the jump command I noticed a long standing bug that points out a
> deficiency with GDB's documentation of the jump command.
>
> The bug points out that 'jump 0x...' is not always the same as 'set
> $pc = 0x...' and then 'continue'. Writing directly to the $pc
> register does not update any auxiliary state, e.g. $npc on SPARC,
> while using 'jump' does.
>
> It felt like this would be an easy issue to address by adding a
> paragraph to the docs, so I took a stab at writing something suitable.
Thanks, this is fine.
Approved-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-04-24 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 16:15 Andrew Burgess
2023-04-24 16:30 ` Eli Zaretskii [this message]
2023-04-27 13:00 ` Andrew Burgess
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=831qk9xmwy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.com \
--cc=gdb-patches@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).