Okay, I've compiled my own version of bash for debugging and managed
to get it to crash with a usable backtrace. It seems to be a problem
with the readline library built into bash-4.3. Just out of curiousity,
why is it we compile bash using its own readline instead of using the
shared library
Using the source I was finally able to figure out a method to
repeatably trigger this heisenbug.
HOW TO REPEAT:
1. echo set revert-all-at-newline on bug.inputrc
2. INPUTRC=bug.inputrc bash
3. ^P^U^N^M [Hold down control and type punm.]
Bash should die immediately with SIGABRT.
DISCUSSION:
Okay, I ran bash under gdb and got a backtrace which perhaps points to
readline. While it's hard to lay blame with a malloc error, this fits
with my experience as bash would often crash immediately after exiting
a command and returning to the prompt.
Josh: Do you have a specialized ~/.inputrc? I
On Wed, Jun 11, 2014 at 09:51:52AM -0700, Ben Wong wrote:
Okay, I ran bash under gdb and got a backtrace which perhaps points to
readline. While it's hard to lay blame with a malloc error, this fits
with my experience as bash would often crash immediately after exiting
a command and returning
4 matches
Mail list logo
