From: Eli Zaretskii <eliz@gnu.org>
To: douglas.j.anderson@gmail.com
Cc: 22657@debbugs.gnu.org
Subject: 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 [thread overview]
Message-ID: <83fuwvz1wr.fsf@gnu.org> (raw)
In-Reply-To: <CAFBY8F35XuFirQOD=1Pe=RsfWBeFRi68_X0o3Zvv5ikvrpMyCQ@mail.gmail.com> (message from Douglas Anderson on Sat, 13 Feb 2016 22:00:49 -0700)
> From: Douglas Anderson <douglasjanderson@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.
next prev parent reply other threads:[~2016-02-14 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 5:00 bug#22657: 24.5; "Python Exception <class 'NameError'> name 'long' is not defined" while using gdb registers buffer Douglas Anderson
2016-02-14 16:34 ` Eli Zaretskii [this message]
2016-02-14 17:22 ` Douglas Anderson
2016-02-14 18:11 ` Eli Zaretskii
2016-02-14 18:20 ` immerrr again
2016-02-14 19:22 ` Douglas Anderson
2016-02-14 19:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fuwvz1wr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22657@debbugs.gnu.org \
--cc=douglas.j.anderson@gmail.com \
/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.