From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Exiting from Python and Guile interpreters
Date: Wed, 16 Dec 2015 10:52:00 -0000 [thread overview]
Message-ID: <83r3im1x7t.fsf@gnu.org> (raw)
I see this in MinGW GDB 7.10 I built myself; I have no access to any
other GDB built with both Python and Guile, so I'm asking here.
It looks like there's an inconsistency in how one should exit from the
Python (entered with "pi") vs Guile (entered with "gr") interpreters
back to GDB:
. to exit Python, one should type the EOF character, Ctrl-D on Unix,
Ctrl-Z on Windows
. typing "quit()" at Python prompt exits the debugger
. to exit Guile, one should type ",q" or ",quit"
. typing the EOF character at Guile prompt exits the debugger
Does this happen on GNU/Linux as well, or is this some Windows
specific problem (perhaps even specific to my build)?
If this is indeed the expected behavior, shouldn't we try making the
two interpreters behave in similar ways?
TIA
next reply other threads:[~2015-12-16 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 10:52 Eli Zaretskii [this message]
2015-12-16 11:16 ` Jan Kratochvil
2015-12-16 11:34 ` 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=83r3im1x7t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox