Changes by Ed Maste <carpedd...@gmail.com>:
--
nosy: +emaste
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue30104>
___
__
Changes by Ed Maste carpedd...@gmail.com:
--
nosy: +emaste
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24520
___
___
Python-bugs-list mailing
Ed Maste added the comment:
I believe the 0-based vs 1-based history is only one of a few different
inconsistencies between libedit and readline. Workarounds will be necessary
until a fixed libedit is deployed on all operating systems / distros of
interest, but yes I agree that eventually
Ed Maste added the comment:
Actually, in msg245395 I should claim the issue is with libedit / GNU readline
compatibility and/or the workarounds in Python's readline module, not that it's
specifically Issue24388.
--
___
Python tracker rep
Ed Maste added the comment:
It looks like rust developers hit the issue in Issue24388 with lldb on Ubuntu
15.04 as well: https://github.com/rust-lang/rust/issues/26297
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13501
Ed Maste added the comment:
Presumably the #ifdefs ought to just be deleted though, relying on the runtime
detection of libedit compatibility issues on any platform.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24388
New submission from Ed Maste:
I encountered a segfault in Python's call_readline from LLDB on FreeBSD, with
libedit. There is a fix for this issue already in readline.c, but under #ifdef
__APPLE__
Backtrace:
(lldb) target create /data/emaste/src/llvm/build/bin/lldb --core
lldb-3.7.0.core
Ed Maste added the comment:
Note that the patch in Issue24388 is more a proof of concept. I'm not sure it's
the right fix.
LLDB is a bit of a special case: LLDB links against libedit, but the Python
libedit module is built as if readline is in use. It turns out this magically
works out
Ed Maste added the comment:
This issue causes the LLDB debugger to crash on FreeBSD (it uses Python as its
embedded script interpreter).
What needs to be done to make some progress on this issue?
--
___
Python tracker rep...@bugs.python.org
http
Changes by Ed Maste carpedd...@gmail.com:
--
nosy: +Ed.Maste
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23458
___
___
Python-bugs-list mailing
Ed Maste added the comment:
For reference, this fd leak was causing one of LLDB's tests to fail. It is now
marked XFAIL pending a resolution of this issue:
http://llvm.org/viewvc/llvm-project?view=revisionrevision=229704
Linux is also affected, the Linux LLDB tests were previously running
Changes by Ed Maste carpedd...@gmail.com:
--
nosy: +Ed.Maste
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15745
___
___
Python-bugs-list mailing
12 matches
Mail list logo