Re: bash segfaults on startup when TERM=eterm* and EMACS is unset

2009-12-09 Thread Roman Rakus
On 10/29/2009 10:35 AM, Roman Rakus wrote: $subject can be triggered easily by setting TERM to eterm (with unset EMACS). Originally this segfault was caused by running emacs and within emacs try to ssh on localhost. Reproducer 1) [rra...@dhcp-lab-170 ~]$ bash [rra...@dhcp-lab-170 ~]$ exit

Re: bash segfaults on startup when TERM=eterm* and EMACS is unset

2009-12-09 Thread Chet Ramey
On 10/29/2009 10:35 AM, Roman Rakus wrote: $subject can be triggered easily by setting TERM to eterm (with unset EMACS). Originally this segfault was caused by running emacs and within emacs try to ssh on localhost. Any updates/comments here? This will be fixed in the next version

bash segfaults on startup when TERM=eterm* and EMACS is unset

2009-10-29 Thread Roman Rakus
$subject can be triggered easily by setting TERM to eterm (with unset EMACS). Originally this segfault was caused by running emacs and within emacs try to ssh on localhost. Reproducer 1) [rra...@dhcp-lab-170 ~]$ bash [rra...@dhcp-lab-170 ~]$ exit [rra...@dhcp-lab-170 ~]$ env TERM=eterm bash