This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Analysis of Mauve failures - The final chapter
Hi,
On Mon, 2002-04-08 at 23:40, Mark Wielaard wrote:
> Hmmm. I am really lost here. I do not even have a clue why the program
> segfaults when run under gdb but seems to terminate normally (although
> without giving output) without gdb. And on another machine with less
> memory it is just killed after a while by the kernel because it gets out
> of memory.
On the other machine I was trying with "normal" big numbers (10000,
16000) when I change the first value of the dimension array to
Integer.MAX_VALUE it gives the same result (silent run or SEGV under
gdb). Replacing the first value with Integer.MAX_VALUE-1 always gives a
SEGV (with or without gdb). And using just a huge value like 2000000000
actually does give OutOfMemoryError!
Small numbers {100,200} -> OK.
Big numbers {10000, 16000} -> Out of swap space, kernel kill.
Huge numbers {2000000000, 1000} -> OutOfMemoryError
Almost MAXINT {Integer.MAX_VALUE-1, Integer.MAX_VALUE} -> SEGV.
MAXINT number {Integer.MAX_VALUE, Intger.MAX_VALUE} -> Silent failure.
So it seems to be some sort of trouble when we are really, really out of
memory and cannot even create an OutOfMemoryError.
Cheers,
Mark