On 2/19/15 4:03 PM, Tobias Stoeckmann wrote:
> These functions would lead to segmentation faults in case of malloc
> failures. Therefore, the return values have to be checked for NULL.
Thanks for the report.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``A
Hi,
When we run the bash unittests on some system we occasionally get a error
in the varenv3.sub script.
./varenv3.sub: cannot open named pipe /tmp/bash_tests.8150/sh-np-5140328 for
writing: No such file or directory
./varenv3.sub: line 30: /tmp/bash_tests.8150/sh-np-843885584: No such file or
On 2/20/15 6:56 AM, Scott wrote:
> Hi,
>
> When we run the bash unittests on some system we occasionally get a error
> in the varenv3.sub script.
>
> ./varenv3.sub: cannot open named pipe /tmp/bash_tests.8150/sh-np-5140328
> for writing: No such file or directory
> ./varenv3.sub: line 30: /tmp/ba
On Fri, Feb 20, 2015 at 09:08:30AM -0500, Chet Ramey wrote:
On 2/20/15 6:56 AM, Scott wrote:
Hi,
When we run the bash unittests on some system we occasionally get a error
in the varenv3.sub script.
./varenv3.sub: cannot open named pipe /tmp/bash_tests.8150/sh-np-5140328
for writing: No such fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/18/15 8:06 AM, Dr. Werner Fink wrote:
> Hi,
>
> found due to a hang in the test suite of gnutls, after debugging I've
> extract the example code
>
> launch_server () { sleep 100 & l=$!; trap "kill -15 $l" 15; echo $l;
> wait $l; }
> l
> Yes. The issue is that the assignment doesn't make the variable visible,
> when it clearly should. I've attached a patch that will fix that.
And it does.
> The next version of bash will do things differently, as noted in a
couple of followups to this message. The proposal that prompted the
cha
On Thu, Feb 19, 2015 at 7:47 PM, Chet Ramey wrote:
> On 2/18/15 4:14 PM, emanuelczi...@cryptolab.net wrote:
>> tl;dr: thanks! no reply needed;
>>
>> Thanks guys. I had a hard time accepting that this is how it's supposed to
>> work.
>> I accepted it now. :)
>
> Yeah. The expression between (( and
