IMHO is the bug on bash side. ash can assume to get an "healthy" environment
from the caller. You can simply not fix everything that can possible go wrong.
Obviously it should not segfault but so far i understand it is bsd as that
does, not busybox ash.
re,
wh
_
Am 18.07.2016 16:36, schrieb Chet Ramey:
> On 7/18/16 10:11 AM, walter harms wrote:
>
>> NTL i would recommend to add one or two line about buffering into
>> the ducomentation :)
>
> It's already documented in the right place:
>
> https://www.gnu.org/so
Am 18.07.2016 15:59, schrieb Greg Wooledge:
> On Mon, Jul 18, 2016 at 10:22:46AM +0200, walter harms wrote:
>> ( ./a.out 2>&1 )
>> hallo 5
>> hallo 6
>> hallo 7
>> hallo 8
>> hallo 9
>
> (snip)
>
>> ./a.out >xx 2>&1
>&
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2
-L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -
hi list,
i noticed that the -p option is described in text (in INVOCATION) but
not in the option list.
re,
wh
hi chet,
#!
may have unexpected side effects. e.g. i got 'unknown interpreter' while
locating a problem.
re,
wh
Chet Ramey wrote:
> walter harms wrote:
>> hi bash-developer,
>> i used the bash test suite to check busybox ash and found
>> two possible
hi bash-developer,
i used the bash test suite to check busybox ash and found
two possible mistakes in the latest release. since the fix
is trivial i did not add a patch.
please add a comment to the source if they are intended.
re,
walter
1. func.tests:FUCNAME=7
possible typo: FUNCNAME ?
2.
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux
Compiler: gcc -I/usr/src/packages/BUILD/bash-3.0
-L/usr/src/packages/BUILD/bash-3.0/../readline-5.0
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i586-
