From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 16366-done@debbugs.gnu.org, andrzej@morgangilbert.co.uk
Subject: bug#16366: 24.3.50; [PATCH] GDB Registers buffer - wrong values fontified
Date: Wed, 26 Jun 2019 19:17:53 +0300 [thread overview]
Message-ID: <83lfxojp72.fsf@gnu.org> (raw)
In-Reply-To: <m35zosz98w.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 26 Jun 2019 16:55:43 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Wed, 26 Jun 2019 16:55:43 +0200
> Cc: 16366@debbugs.gnu.org
>
> > $ 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:
Your GDB seems to be misconfigured wrt its Python extensions.
I've reproduced the problem, verified that the proposed patch fixes
it, and installed it on the master branch.
Andrzej, apologies for such a long delay in fixing this simple
problem, and thanks for the patch.
prev parent reply other threads:[~2019-06-26 16:17 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
2019-06-26 16:17 ` Eli Zaretskii [this message]
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=83lfxojp72.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16366-done@debbugs.gnu.org \
--cc=andrzej@morgangilbert.co.uk \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.