unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jonas Bülow" <jonas.bulow@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63855@debbugs.gnu.org
Subject: 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	[thread overview]
Message-ID: <CAEGOEeWUS54J3nQPBP22q89NPWgSYZv==k2k7eNMQGm+fhddXg@mail.gmail.com> (raw)
In-Reply-To: <83pm6dafop.fsf@gnu.org>

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@gnu.org> wrote:
>
> > From: Jonas Bülow <jonas.bulow@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.)





  reply	other threads:[~2023-06-03 10:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 16:00 bug#63855: 29.0.91; Exiting gdb's python interactive mode within gud-mode exits gdb as well Jonas Bülow
2023-06-02 18:21 ` Eli Zaretskii
2023-06-03 10:10   ` Jonas Bülow [this message]
2023-06-03 10:36     ` Eli Zaretskii
2023-06-03 11:11       ` Eli Zaretskii
2023-06-03 11:22         ` Jonas Bülow

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEGOEeWUS54J3nQPBP22q89NPWgSYZv==k2k7eNMQGm+fhddXg@mail.gmail.com' \
    --to=jonas.bulow@gmail.com \
    --cc=63855@debbugs.gnu.org \
    --cc=eliz@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).