From: Simon Marchi <simark@simark.ca>
To: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: Discrepancy between Python and Guile wrt exiting the interpreter
Date: Sun, 19 Jan 2020 16:11:00 -0000 [thread overview]
Message-ID: <c3809720-3247-3bc4-c67e-8b7b133691a6@simark.ca> (raw)
In-Reply-To: <83a76l10r6.fsf@gnu.org>
On 2020-01-18 6:07 a.m., Eli Zaretskii wrote:
> If you invoke the Guile interpreter from GDB:
>
> (gdb) gr
>
> then typing ,q followed by Enter exits the Guile interpreter back to
> GDB. However, if the Python interpreter is started:
>
> (gdb) pi
>
> then typing quit() and Enter exits GDB, not just the Python
> interpreter. Why do these two interpreters behave differently in this
> context? Is there some other Python command to exit the interpreter?
> (I know about Ctrl-D, but I'm asking about commands.)
>
> Thanks.
>
I looked into it, but didn't find a way to exit the Python interpreter and
come back in GDB by typing a Python command. That command would somehow
have to fool the Python interpreter in thinking that its input stream, which
we pass here:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob;f=gdb/python/python.c;h=d6f7f99c457300cba8e6dbe590ac15b4b2e2b110;hb=HEAD#l302
has reached EOF.
I'm not saying it can't be done, just that I haven't found a way.
Simon
next prev parent reply other threads:[~2020-01-19 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 14:46 Eli Zaretskii
2020-01-19 16:11 ` Simon Marchi [this message]
2020-01-19 16:42 ` Eli Zaretskii
2020-01-19 17:20 ` Simon Marchi
2020-01-19 19:13 ` Eli Zaretskii
2020-01-21 19:53 ` Tom Tromey
2020-01-21 19:57 ` Eli Zaretskii
2020-01-23 17:21 ` Pedro Alves
2020-01-23 17:37 ` Simon Marchi
2020-01-23 17:50 ` Pedro Alves
2020-01-23 17:39 ` Pedro Alves
2020-01-24 10:26 ` Eli Zaretskii
2020-01-23 18:20 ` Eli Zaretskii
2020-01-23 18:30 ` Pedro Alves
2020-01-23 18:46 ` 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=c3809720-3247-3bc4-c67e-8b7b133691a6@simark.ca \
--to=simark@simark.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@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