[Converted from Gnats 841] http://sources.redhat.com/gdb/current/onlinedocs/gdb_15.html#IDX545 Doco should mention that, on some architectures, 'jump ...' actually sets $pc and $npc (and well if I'd not deleted the 88k) $nnpc. Or to put it another way 'set $pc = ...' is not portable across architectures. Release: unknown
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0d42948f0c822ed3782a45771c8fbc21aa2d6553 commit 0d42948f0c822ed3782a45771c8fbc21aa2d6553 Author: Andrew Burgess <aburgess@redhat.com> Date: Mon Apr 24 15:27:27 2023 +0100 gdb/doc: extend the documentation of the jump command 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. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=7946 Approved-By: Eli Zaretskii <eliz@gnu.org>
I believe this is now resolved.