Your message dated Fri, 29 May 2015 13:36:32 +0200
with message-id
<CA+7wUsyT5r8cmP9rkG8c+UE6Zep_P54TEi-t0jJ5c0TYGsK=p...@mail.gmail.com>
and subject line Fixed
has caused the Debian Bug report #725707,
regarding xmalloc: ../../../bash/lib/sh/stringvec.c:40: cannot allocate
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
725707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725707
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bash
I would be nice if the behavior was a little more tolerant than just a
seg fault for something like:
$ bash
$ bash
$ for i in {1..1000000000}; do uptime; done
bash: xmalloc: ../../../bash/lib/sh/stringvec.c:40: cannot allocate
8000000008 bytes (3829760 bytes allocated)
$ echo $?
2
Thanks
--- End Message ---
--- Begin Message ---
fixed -1 4.3-11+b1
thanks
New -nicer- behavior:
$ for i in {1..1000000000}; do uptime; done
bash: brace expansion: failed to allocate memory for 1000000000 elements
13:35:35 up 3:33, 16 users, load average: 0.19, 0.17, 0.18
--- End Message ---
