On Tue, Nov 02, 2010 at 03:48:49PM -0400, Pete Gregory wrote:
> echo {2147483640..2147483647}
> dies with a malloc error
In bash 4.1.9 under HP-UX 10.20, it consumes all available CPU until
I kill it with SIGKILL. (I suppose there's a chance it might eventually
have died due to malloc errors or w
> echo {2147483640..2147483647}
> dies with a malloc error
I suggest that Linux kids do not try this at home: the OutOfMemory killer
killed a few random processes of mine!
Greg Wooledge wrote:
On Tue, Nov 02, 2010 at 03:48:49PM -0400, Pete Gregory wrote:
echo {2147483640..2147483647}
dies with a malloc error
In bash 4.1.9 under HP-UX 10.20, it consumes all available CPU until
I kill it with SIGKILL. (I suppose there's a chance it might eventually
have died due
Marc Herbert wrote:
> I suggest that Linux kids do not try this at home: the OutOfMemory killer
> killed a few random processes of mine!
Off-Topic for this mailing list but if so then you should configure
your Linux kernel to avoid memory overcommit. I have previously
ranted about this in some de
Hi Bob,
Thank you for the information.
I have experienced this OOM killer 2 years ago while handling a Linux
server running a big Oracle database.
It's really hard to troubleshoot what is the cause of sudden missing
of Oracle process, with no trace in any log, until one of our in-house
Linux gur
Even with a 64-bit kernel, under bash4.1-2 under ubuntu 10.04, problems exist
with numbers beyond 2147483646.
Easy duplication method:
echo {2147483640..2147483646}
reports
2147483640 2147483641 2147483642 2147483643 2147483644 2147483645 2147483646
echo {2147483640..2147483647}
dies with a mall
