Am Mittwoch, den 26.11.2008, 09:51 +0800 schrieb [EMAIL PROTECTED]:
> There are many times one has not planned ahead, and forgets the &:
> $ emacs -nw important.txt #then after a half an hour of editing:
> ^Z
> [1]+ Stopped emacs -nw important.txt
> $ compact_disk_burner_GUI_applic
On Wed, Nov 26, 2008 at 09:51:13AM +0800, [EMAIL PROTECTED] wrote:
> There are many times one has not planned ahead, and forgets the &:
> $ emacs -nw important.txt #then after a half an hour of editing:
> ^Z
> [1]+ Stopped emacs -nw important.txt
> $ compact_disk_burner_GUI_applica
There are many times one has not planned ahead, and forgets the &:
$ emacs -nw important.txt #then after a half an hour of editing:
^Z
[1]+ Stopped emacs -nw important.txt
$ compact_disk_burner_GUI_application #forgot to add &
OK, we want to get back to emacs, but we dare not stop
Barry Davis wrote:
> bash# echo $BASH_VERSION
> 2.05b.0(1)-release
> bash# fn() { local x; unset x; echo [EMAIL PROTECTED] ; echo [EMAIL
> PROTECTED]; }
> bash# fn
> 1
>
> ran in a script you get a SEGV
> ran interactively it hangs.
Bash-2.05b is three versions behind and not maintained. Please
[EMAIL PROTECTED] wrote:
> hello,
>
> i made some observation by chance.
>
> bash 3.2 seems to leak environment variables into open() syscalls (older bash
> 2.0 does not show this behaviour)
Bash isn't doing the opens -- they're coming from the libc locale code.
--
``The lyf so short, the c
i forgot to tell that it doesn`t happen with every locale.
you have to set it like this to reproduce:
vmhost:/usr/src/packages/SOURCES/bash-3.2 # locale
LANG=
LC_CTYPE=de_DE.UTF-8
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAM
hello,
i made some observation by chance.
bash 3.2 seems to leak environment variables into open() syscalls (older bash
2.0 does not show this behaviour)
this may not be an issue here or do not any harm - but at least opening such
non-existing files is nonsense and it really looks like a bug
bash# echo $BASH_VERSION
2.05b.0(1)-release
bash# fn() { local x; unset x; echo [EMAIL PROTECTED] ; echo [EMAIL PROTECTED];
}
bash# fn
1
ran in a script you get a SEGV
ran interactively it hangs.
