>> It seems that the high bits should be more random. If so, maybe the
>> high 16 bits should be kept if $RANDOM must stay in 16bits?
>
>This seems like something you could test and verify.
This aroused my curiosity, so I passed the generator's output through
dieharder (https://webhome.phy.duke.ed
On 5/14/19 5:57 PM, Yu Kou wrote:
> Bash Version: 5.0
> Patch Level: 2
> Release Status: release
>
> Description:
> This bug was found in bash 4.4.12 (GNU bash, version
> 4.4.12(1)-release (x86_64-pc-linux-gnu))
> It is still here in bash 5.0.2.
>
> I pubilshed it first i
On 5/15/19 5:46 AM, Andrew Church wrote:
>>> I assume this is a valgrind false positive.
>>
>> That possible. However, the assertion that causes the abort, is part of
>> the malloc.c version (line 934) that ships with bash. I guess that the
>> issue is caused by the fact that bash uses it's own mal
>> I assume this is a valgrind false positive.
>
>That possible. However, the assertion that causes the abort, is part of
>the malloc.c version (line 934) that ships with bash. I guess that the
>issue is caused by the fact that bash uses it's own malloc.c, which
>seems to be incompatible with valgr
On 14.05.19 15:46, Chet Ramey wrote:
I assume this is a valgrind false positive.
That possible. However, the assertion that causes the abort, is part of
the malloc.c version (line 934) that ships with bash. I guess that the
issue is caused by the fact that bash uses it's own malloc.c, which
