bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Seq Segment Fault.


From: Eric Blake
Subject: Re: Seq Segment Fault.
Date: Fri, 18 Sep 2009 05:58:39 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Ryan Whited on 9/18/2009 4:38 AM:
> #!/bin/bash
> for i in $(seq -w $NUM1 $NUM2)

Are you sure your segfault is in seq, or is it in bash?  You neglected to
mention which versions you were using:

bash --version
seq --version

However, it seems to me that your problem is that bash tries to slurp all
of $() into memory, and seq generated so much data that bash ran out of
memory (or overflowed its stack).  In other words, it is not a segfault in
seq, but bash that crashed, and because you exceeded the limits of what
your machine will support.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqzde8ACgkQ84KuGfSFAYAbHgCgnNr01KRBNuhsC2ifQOEcgx4f
okQAn2i/cc4inQM46UOq5WeMAsxJnwpj
=s0aj
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]