From: Pedro Alves <palves@redhat.com>
To: Matthias Klose <doko@ubuntu.com>,
gdb-patches@sourceware.org, John Baldwin <jhb@freebsd.org>
Subject: Re: [patch] Allow to link with ncursesw
Date: Wed, 20 Sep 2017 21:25:00 -0000 [thread overview]
Message-ID: <b2b763ba-a4e0-3dab-9cf8-659cae3a839b@redhat.com> (raw)
In-Reply-To: <e8d80005-3c3a-cff7-0164-858280117d89@redhat.com>
On 09/20/2017 10:22 PM, Pedro Alves wrote:
> On 09/20/2017 08:51 PM, Matthias Klose wrote:
>> Python itself doesn't link to a curses library, it uses the only which is used
>> for readline.
>>
>
> And if readline doesn't use curses, what does Python do?
Hmm, maybe Python is not relevant here, because we have,
in gdb/python/py-gdb-readline.c:
/* Initialize Python readline support. */
void
gdbpy_initialize_gdb_readline (void)
{
/* Python's readline module conflicts with GDB's use of readline
since readline is not reentrant. Ideally, a reentrant wrapper to
GDB's readline should be implemented to replace Python's readline
and prevent conflicts. For now, this file implements a
sys.meta_path finder that simply fails to import the readline
module. */
That still leaves open the question about non-GNU/Linux OSs, though.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-09-20 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 10:29 Matthias Klose
2017-09-20 18:39 ` Pedro Alves
2017-09-20 19:52 ` Matthias Klose
2017-09-20 21:22 ` Pedro Alves
2017-09-20 21:25 ` Pedro Alves [this message]
2017-09-20 23:58 ` John Baldwin
2017-09-22 10:22 ` Pedro Alves
2017-09-25 18:34 ` John Baldwin
2017-09-26 15:27 ` 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=b2b763ba-a4e0-3dab-9cf8-659cae3a839b@redhat.com \
--to=palves@redhat.com \
--cc=doko@ubuntu.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.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