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 to the prompt.
While I can't easily distinguish the two cases (since my terminal tabs close
when the shell does, and I don't usually run the shell under gdb or under
another shell), the crash always occurs for me when I press enter on a newly
typed command line. The memory corruption may linger from some previous
command, but the crash doesn't happen until I type in a new command and hit
enter.
> Josh: Do you have a specialized ~/.inputrc? I do and I wonder if that
> could be what's triggering the bug for us. A lesser possibility could
> be a customized prompt. Have you changed your PS1 from Debian's
> default?
>
> My PS1='\h:\W\$ '
>
> My .inputrc follows
[...]
Yes, I have a custom PS1 and .inputrc. You can git clone all of my
relevant configuration files from git://joshtriplett.org/git/home .
Here's my PS1:
\[\e]0;\w\a\]$(e="$?";[ "$e" -ne 0 ] && echo -n "\[\e[01;31m\]($e)
")${debian_chroot:+\[\e[01;37m\]($debian_chroot)
}${prompt_remote:+\[\e[01;32m\]\u@\h\[\e[00m\]:}\[\e[01;34m\]\w\[\e[00m\]\$
\[$(__vte_osc7)\]
Here's my .inputrc:
$include /etc/inputrc
set editing-mode emacs
set bell-style none
"\e[1~": beginning-of-line
"\e[4~": end-of-line
"\e[1;5C": forward-word
"\e[1;5D": backward-word
"\e[5C": forward-word
"\e[5D": backward-word
"\e\e[C": forward-word
"\e\e[D": backward-word
$if term=rxvt
"\e[8~": end-of-line
"\eOc": forward-word
"\eOd": backward-word
$endif
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
