[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-30 Thread Shlomi Fish
Shlomi Fish added the comment: Marting Panter: I'm getting the same problem with a completely empty ~/.python_history file. Moreover, I was able to reproduce a similar bug in gdb. I'll try seeing if I can create a minimal GNU readline-using program here that reproduces it. --

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-30 Thread Shlomi Fish
Shlomi Fish added the comment: Martin: [sorry for misspelling your name] I was now able to reproduce the same problem using rlwrap (see http://utopia.knoware.nl/~hlub/rlwrap/ ). I'll report it to the readline problem. -- ___ Python tracker

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-30 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- resolution: - third party stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24958 ___

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread R. David Murray
R. David Murray added the comment: Sorry, should have been clearer a bug in python as opposed to one in Mageia's readline. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24958 ___

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread Shlomi Fish
New submission from Shlomi Fish: After I run python3 (to run the REPL) and type r and then PgUp twice, I get a segfault. I'm on Mageia Linux x86-64 6 , but recall a similar problem happening before: shlomif@telaviv1:~$ python3 Python 3.4.3 (default, Aug 13 2015, 21:40:54) [GCC 4.9.2] on

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread R. David Murray
R. David Murray added the comment: What makes you think this is a bug in Python? Can you reduce the inputrc to the minimum that reproduces the problem? -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread Shlomi Fish
Shlomi Fish added the comment: I'm attaching here the reduced, minimal, inputrc. I think it's a bug in Python because it doesn't happen with any other program that uses readline (bash, perl -d, etc.) that I checked. I'll check with a vanilla readline compiled from source from the GNU site ,

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread R. David Murray
R. David Murray added the comment: I can't reproduce it on my Gentoo box using 3.4 tip. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24958 ___

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread Shlomi Fish
Shlomi Fish added the comment: Hi all! Thanks for the investigation. I have now built readline-6.3 from source using: ./configure --prefix=$HOME/apps/readline-TO_DEL --with-curses=yes --enable-multibyte and installed it. Then I built python 3.4.3 from source against it by setting

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread Martin Panter
Martin Panter added the comment: Well it looks like you’ve identified that PgUp triggers a history search. Perhaps it would be good to look at your /home/shlomif/.python_history file, assuming there is nothing sensitive in there. The strace output only indicates it is 411 bytes and gives the

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread Martin Panter
Martin Panter added the comment: According to the GDB backtrace, _rl_kscxt is a null pointer at https://github.com/Distrotech/readline/blob/readline-6.3/callback.c#L188, while the _rl_dispatch_callback() function doesn’t handle null pointers. Maybe you would find the Readline people more

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread eryksun
eryksun added the comment: Maybe the problem is using escape characters (0x1b) instead of \e. Try using the following: \e[5~: history-search-backward FWIW, your inputrc doesn't crash my system (64-bit Linux, readline 6.3 and Python 3.4). -- nosy: +eryksun

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread eryksun
eryksun added the comment: A gdb backtrace may be of more help than strace. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24958 ___ ___

[issue24958] Segfault in REPL after pressing r and PgUp twice (on Mageia Linux x86-64 6)

2015-08-29 Thread Shlomi Fish
Shlomi Fish added the comment: gdb by full attached. -- Added file: http://bugs.python.org/file40296/py3.gdb-bt.txt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24958 ___