On 12/22/2015 03:38 PM, Chet Ramey wrote:
On 12/21/15 7:38 PM, Carlo Milanesi wrote:Bash Version: 4.3 Patch Level: 11 Release Status: release Description: Every time I insert a character in a command-line in a position followed by some characters and some blanks, Bash crashes. Repeat-By: In a new command line, if I type the following 4 keys: [a][SPACE][HOME][s] the Bash process terminates printing "Segmentation fault". This happens both in a Gnome terminal window, and in a text-mode screen.I can't reproduce this. Can you get a stack traceback of the core dump or attach to the bash process using gdb before it crashes and print the stack traceback (using `where') when it crashes?
Here it is: Program received signal SIGSEGV, Segmentation fault. 0x00000000004a5073 in ?? () (gdb) where #0 0x00000000004a5073 in ?? () #1 0x00000000004a64d5 in rl_redisplay () #2 0x00000000004951de in _rl_internal_char_cleanup () #3 0x00000000004959e9 in readline_internal_char () #4 0x0000000000496075 in readline () #5 0x00000000004215da in ?? () #6 0x0000000000423836 in ?? () #7 0x0000000000426712 in ?? () #8 0x0000000000429cf4 in yyparse () #9 0x0000000000420eeb in parse_command () #10 0x0000000000420fbc in read_command () #11 0x00000000004211b9 in reader_loop () #12 0x000000000041f759 in main ()
