[lldb-dev] suspect bug: lldb segfault when redirecting `--version` output

Ed Maste emaste at freebsd.org
Mon Jun 15 10:44:35 PDT 2015


On 15 June 2015 at 02:18, Alexander Samoilov
<alexander.samoilov at googlemail.com> wrote:
> Hi All,
>
> Stumbled upon the following behavior:
>
> ```sh
> $ /usr/bin/lldb --version
> lldb version 3.6.0 ( revision )
> ```
> ok, but
> ```
> /usr/bin/lldb --version  >& LLDB.VERS
> Segmentation fault (core dumped)
> ```
> Suspect a bug, debugged it a bit, failed in `wcscmp ()`

Have a look at http://bugs.python.org/issue13501 and issues referenced
from there. There have been a number of inconsistencies between
libedit's readline compatibility interface and GNU readline, and
Python's readline module has workarounds for a number of these but
only for __APPLE__.

I suspect that on OS X the standard Python expects libedit, not
readline, and everything "just works" with the built-in workarounds.
On other platforms Python may be built assuming readline, but then it
actually gets libedit via LLDB. The readline module can detect at
runtime that the workarounds are necessary -- it just need to be
enabled for all operating systems, I think.



More information about the lldb-dev mailing list