STINNER Victor added the comment: Python uses an user handler "rlhandler()" which calls rl_callback_handler_remove(). Is it safe to call rl_callback_handler_remove() in an user handler?
Traceback on the crash: Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () (gdb) where #0 0x0000000000000000 in ?? () #1 0x0000003d0c22d67e in rl_callback_read_char () at ../callback.c:238 #2 0x00007ffff149ce85 in readline_until_enter_or_signal (prompt=prompt@entry=0x7ffff17ef598 "(Cmd) ", signal=signal@entry=0x7fffffffd52c) at /home/haypo/prog/python/default/Modules/readline.c:1143 #3 0x00007ffff149cfaa in call_readline (sys_stdin=0x3cecfba8e0 <_IO_2_1_stdin_>, sys_stdout=0x3cecfbb620 <_IO_2_1_stdout_>, prompt=0x7ffff17ef598 "(Cmd) ") at /home/haypo/prog/python/default/Modules/readline.c:1231 #4 0x00000000005ae97a in PyOS_Readline (sys_stdin=0x3cecfba8e0 <_IO_2_1_stdin_>, sys_stdout=0x3cecfbb620 <_IO_2_1_stdout_>, prompt=0x7ffff17ef598 "(Cmd) ") at Parser/myreadline.c:211 #5 0x000000000052ec57 in builtin_input_impl (module=module@entry=0x7ffff189bc58, prompt=<optimized out>) at Python/bltinmodule.c:1924 #6 0x000000000052f054 in builtin_input (module=0x7ffff189bc58, args=<optimized out>) at Python/clinic/bltinmodule.c.h:546 (...) Other trace with source code of readline: Program received signal SIGSEGV, Segmentation fault. 0x0000000000000000 in ?? () Missing separate debuginfos, use: dnf debuginfo-install ncurses-libs-5.9-18.20150214.fc22.x86_64 (gdb) up #1 0x0000003d0c22d67e in rl_callback_read_char () at ../callback.c:238 238 (*rl_linefunc) (line); (gdb) print rl_linefunc $1 = (rl_vcpfunc_t *) 0x0 ---------- nosy: +haypo _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25259> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com