GNU bug report logs - #22657
24.5; "Python Exception <class 'NameError'> name 'long' is not defined" while using gdb registers buffer

Previous Next

Package: emacs;

Reported by: douglas.j.anderson <at> gmail.com

Date: Sun, 14 Feb 2016 07:10:02 UTC

Severity: normal

Found in version 24.5

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 22657 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: douglas.j.anderson <at> gmail.com
Cc: 22657 <at> debbugs.gnu.org
Subject: Re: bug#22657: 24.5;
 "Python Exception <class 'NameError'> name 'long' is not defined"
 while using gdb registers buffer
Date: Sun, 14 Feb 2016 18:34:28 +0200
> From: Douglas Anderson <douglasjanderson <at> gmail.com>
> Date: Sat, 13 Feb 2016 22:00:49 -0700
> 
> I'm using current stable on Ubuntu 15.10.
> 
> Steps to reproduce:
> - open emacs gdb-many-windows mode (I only hit this bug if the registers
> buffer is open)
> - set a breakpoint
> - run
> 
> The following text appears in the gud window:
> (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: 
> 
> Hitting enter reruns the program from the beginning.

I cannot reproduce this.  Please show the exact sequence of commands
you used, including the program which you ran under the debugger, for
me to be sure I did the same.

Also, what is your GDB version?

IME, Python exceptions in GDB usually mean your Python support files
are from a different GDB version, so perhaps double-check your GDB
installation.

Thanks.




This bug report was last modified 9 years and 162 days ago.

Previous Next


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