Arch Linux

Description:

When using ipython2, I get a segfault in the readline library. Not sure what package to report this to, but it seems like readline is the culprit. Downgrading readline from 6.3 to 6.2 solves the problem.


Additional info:
* package version: readline-6.3-1


Steps to reproduce:
1. Open ipython2
2. Type "import"
3. press up, down, up.
4. You should get a segfault.

Relevant Valgrind log (running valgrind ipython2 and doing the steps above):

In [1]: import==11170== Invalid read of size 1 ND
==11170== at 0xD351849: _rl_dispatch_callback (in /usr/lib/libreadline.so.6.3)
==11170== by 0xD367C9F: rl_callback_read_char (in /usr/lib/libreadline.so.6.3)
==11170== by 0xD1359B4: ??? (in /usr/lib/python2.7/lib-dynload/readline.so)
==11170== by 0x4E7639F: PyOS_Readline (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F06506: builtin_raw_input (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F10758: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F111AF: PyEval_EvalCodeEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F103A8: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F111AF: PyEval_EvalCodeEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F103A8: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F111AF: PyEval_EvalCodeEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F103A8: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==11170==
==11170==
==11170== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==11170== Access not within mapped region at address 0x0
==11170== at 0xD351849: _rl_dispatch_callback (in /usr/lib/libreadline.so.6.3)
==11170== by 0xD367C9F: rl_callback_read_char (in /usr/lib/libreadline.so.6.3)
==11170== by 0xD1359B4: ??? (in /usr/lib/python2.7/lib-dynload/readline.so)
==11170== by 0x4E7639F: PyOS_Readline (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F06506: builtin_raw_input (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F10758: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F111AF: PyEval_EvalCodeEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F103A8: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F111AF: PyEval_EvalCodeEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F103A8: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F111AF: PyEval_EvalCodeEx (in /usr/lib/libpython2.7.so.1.0)
==11170== by 0x4F103A8: PyEval_EvalFrameEx (in /usr/lib/libpython2.7.so.1.0)
==11170== If you believe this happened as a result of a stack
==11170== overflow in your program's main thread (unlikely but
==11170== possible), you can try to increase the size of the
==11170== main thread stack using the --main-stacksize= flag.
==11170== The main thread stack size used in this run was 8388608.