On Mon, Feb 3, 2014 at 2:22 PM, Greg Wooledge wrote:
> On Sat, Feb 01, 2014 at 05:36:17PM +0100, Mathieu Malaterre wrote:
>> #!/bin/bash
>>
>> for i in {0..4294967295}; do
>> echo $i
>> done
>
> Others said not to do that. They are correct, but th
As reported at:
http://stackoverflow.com/questions/21500367/bash-for-loop-with-unsigned-integer
I am getting a weird behavior in bash. Would it be possible for the
next release of bash to not get a SIGSEV ?
Steps:
#!/bin/bash
for i in {0..4294967295}; do
echo $i
done
Thanks,
--
Mathieu
