From: Tom Tromey <tromey@redhat.com>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4]: Enable readline under "python"
Date: Wed, 25 Jul 2012 17:38:00 -0000 [thread overview]
Message-ID: <87boj3ivw7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <A7A972B1-3B6B-4A99-BB64-6CC32C7FE448@cs.umd.edu> (Khoo Yit Phang's message of "Mon, 16 Jul 2012 17:04:16 -0400")
>>>>> "Yit" == Khoo Yit Phang <khooyp@cs.umd.edu> writes:
Yit> 1) either reimplement the readline module that carefully swaps
Yit> configurations between GDB and Python; 2) or run Python's readline in
Yit> a separate controlling terminal with a proxy readline module in GDB.
#2 seems extremely hard.
Maybe #1 is possible, I don't know.
Yit> 2012-07-16 Khoo Yit Phang <khooyp@cs.umd.edu>
Yit> Enable readline in Python in a GDB-specific way and block the
Yit> standard Python readline module to prevent conflicts with GDB.
Yit> * Makefile.in (SUBDIR_PYTHON_OBS): Add py-gdb-readline.o.
Yit> (SUBDIR_PYTHON_SRCS): Add python/py-gdb-readline.c.
Yit> (py-gdb-readline.o): Add rule to compile python/py-gdb-readline.c.
Yit> * python/py-gdb-readline.c: New file.
Yit> * python/python-internal.h (gdbpy_initialize_gdb_readline): New
Yit> prototype.
Yit> * python/python.c (_initialize_python): Call
Yit> gdbpy_initialize_gdb_readline.
This one is ok; but of course it depends on an earlier patch so it can't
go in until that is resolved.
Tom
next prev parent reply other threads:[~2012-07-25 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 21:04 Khoo Yit Phang
2012-07-25 17:38 ` Tom Tromey [this message]
2012-08-22 19:39 ` Khoo Yit Phang
2012-08-22 19:55 ` Tom Tromey
2012-08-23 11:21 ` Kevin Pouget
2012-08-23 13:04 ` Khoo Yit Phang
2012-08-23 13:15 ` Kevin Pouget
2012-08-24 1:42 ` Khoo Yit Phang
2012-08-24 8:55 ` Pedro Alves
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=87boj3ivw7.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=khooyp@cs.umd.edu \
/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