GNU bug report logs - #16366
24.3.50; [PATCH] GDB Registers buffer - wrong values fontified

Previous Next

Full log

Message #13 received at 16366-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 16366-done <at> debbugs.gnu.org, andrzej <at> morgangilbert.co.uk
Subject: Re: bug#16366: 24.3.50;
 [PATCH] GDB Registers buffer - wrong values fontified
Date: Wed, 26 Jun 2019 19:17:53 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Wed, 26 Jun 2019 16:55:43 +0200
> Cc: 16366 <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.