All I have installed else is dash: 4 successes 0 failures.
SC> perl -e '$<=$>=$(=$)=65534; exec sh'
That gets a shell without triggering the error.
SC> perl -e '$<=$>=$(=$)=65534; system sh'
That filled emacs with \377's with luckily a little CPU left over that
I could kill emacs... *
SC> Not sure how what bash_completion does could have an impact on su.
I observed the bug with and without the bash-completion package installed.
# lsof -p $$|wc -l
18
pstree shows no processes running left behind.
I observe the bug with both mesg y and n
SC> running out of ideas here...
Me too so I hereby wait for Sven to chime in with what else he sees.
*This side issue only happened in emacs's shell, (and not with
LC_ALL=C, but yes with my zh locale) and is one of the reasons I now
use a different HISTORY file there... piped thru cat -v.
# sleep 22 && kill -1 $$& #Safety first, also makes the \377s go away.
[1] 16017
# perl -we '$<=$>=$(=$)=65534;system q(sh)'
05:40 ~$ Use "exit" to leave the shell.
05:40 ~$ sh: syntax error near unexpected token `('
05:40 258 ~$ sh:[EMAIL PROTECTED]: command not found
05:40 127 ~$ sh: syntax error near unexpected token `('
Anyway, no I don't believe in UFOs. Never mind this side issue. Bye.
