diff options
| author | Simon Ochsenreither <simon@ochsenreither.de> | 2013-11-22 20:02:08 +0100 |
|---|---|---|
| committer | Simon Ochsenreither <simon@ochsenreither.de> | 2013-11-22 20:02:08 +0100 |
| commit | 64603653f82082431941cb29ad317b669822f28e (patch) | |
| tree | a0be7a449a31414e5e2c1fe05fc7378d82aaf02c /test/files/jvm | |
| parent | ad5fa95d55096e498c461471528d957ffc82706c (diff) | |
| download | scala-64603653f82082431941cb29ad317b669822f28e.tar.gz scala-64603653f82082431941cb29ad317b669822f28e.tar.bz2 scala-64603653f82082431941cb29ad317b669822f28e.zip | |
SI-7999 s.u.c.NonFatal: StackOverflowError is fatal
As demonstrated in
https://groups.google.com/d/topic/scala-language/eC9dqTTBYHg, SOEs
should be considered fatal, because all popular JVM implementations
seem to run into inconsistent state (ignoring finally blocks leading
to not running monitorExit, leading to locks not being unlocked, ...)
if one just pushes them enough.
Diffstat (limited to 'test/files/jvm')
| -rw-r--r-- | test/files/jvm/non-fatal-tests.scala | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/files/jvm/non-fatal-tests.scala b/test/files/jvm/non-fatal-tests.scala index 791b1d3100..1ff7ee516e 100644 --- a/test/files/jvm/non-fatal-tests.scala +++ b/test/files/jvm/non-fatal-tests.scala @@ -4,8 +4,7 @@ trait NonFatalTests { //NonFatals val nonFatals: Seq[Throwable] = - Seq(new StackOverflowError, - new RuntimeException, + Seq(new RuntimeException, new Exception, new Throwable, new NotImplementedError) @@ -13,6 +12,7 @@ trait NonFatalTests { //Fatals val fatals: Seq[Throwable] = Seq(new InterruptedException, + new StackOverflowError, new OutOfMemoryError, new LinkageError, new VirtualMachineError {}, |