From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrzej P <andrzej@morgangilbert.co.uk>
Cc: 16366@debbugs.gnu.org
Subject: bug#16366: 24.3.50; [PATCH] GDB Registers buffer - wrong values fontified
Date: Wed, 26 Jun 2019 16:55:43 +0200 [thread overview]
Message-ID: <m35zosz98w.fsf@gnus.org> (raw)
In-Reply-To: <87bnzqvtfr.fsf@andrzej-laptop.i-did-not-set--mail-host-address--so-tickle-me> (Andrzej P.'s message of "Mon, 06 Jan 2014 00:35:04 +0000")
Andrzej P <andrzej@morgangilbert.co.uk> writes:
> When stepping through a program with the GDB graphical interface, the
> values in the Registers buffer are fontified with
> 'font-lock-warning-face' on the step *after* they have changed. It
> makes more sense to highlight changed values on each step. I guess
> that this is a bug.
>
> To reproduce:
>
> $ emacs -Q
>
> M-x gdb
>
> gdb -i=mi emacs <return> (or something suitable)
>
> M-x gdb-display-registers-buffer
>
> In GUD buffer:
>
> (gdb) break main
> (gdb) run
>
> Now step by machine instructions (e.g. 'C-x C-a C-i'). The values of
> registers in the Registers buffer change but are fontified only on the
> following step.
I tried to reproduce this, but all I got was a bunch of
Breakpoint 3, main (argc=1, argv=0x7fffffffe9e8) at emacs.c:977
977 {
(gdb) Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
(gdb) Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
Python Exception <class 'NameError'> name 'long' is not defined:
in the *gud-emacs* buffer...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-06-26 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 0:35 bug#16366: 24.3.50; [PATCH] GDB Registers buffer - wrong values fontified Andrzej P
2019-06-26 14:55 ` Lars Ingebrigtsen [this message]
2019-06-26 16:17 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m35zosz98w.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=16366@debbugs.gnu.org \
--cc=andrzej@morgangilbert.co.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).