GNU bug report logs - #63855
29.0.91; Exiting gdb's python interactive mode within gud-mode exits gdb as well

Previous Next

Full log

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

From: Jonas Bülow <jonas.bulow <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 63855 <at> debbugs.gnu.org
Subject: Re: bug#63855: 29.0.91; Exiting gdb's python interactive mode within
 gud-mode exits gdb as well
Date: Sat, 3 Jun 2023 12:10:04 +0200

Unfortunately, there doesn't seem to be any other way to exit python
interactive mode. Using exit() or quit() from python interactive mode
exits gdb even from the terminal.

On Fri, Jun 2, 2023 at 8:20 PM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > From: Jonas Bülow <jonas.bulow <at> gmail.com>
> > Date: Fri, 2 Jun 2023 18:00:33 +0200
> >
> > 0. (start with emacs -Q)
> > 1. M-x gdb <RET>
> > 2. Run gdb (like this): gdb -i=mi <RET>
> > 3. Enter python interactive mode with: pi <RET>
> > 4. Try to exit gdb's python interactive mode with Ctrl-D
> >
> > Expected: get back to gdb prompt
> >
> > Actual: gdb exits with "Debugger finished"
>
> AFAIR, this is the best we can do in that situation.  You should exit
> python interactive mode by other means, if you want to stay inside
> GDB.  Sorry.
>
> (Of course, if someone knows how to teach gdb-mi.el to distinguish
> between the two possible interpretations of EOF, patches to do so will
> be welcome.)

Previous Next

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