Author stefan.richthofer
Recipients jamesmudd, jeff.allen, stefan.richthofer, zyasoft
Date 2017-03-30.12:16:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> What makes you think the StackOverflowError thrown in the finally doesn't propagate up the stack?

It also occurred to me that an earlier call of recursion would handle the subsequent StackOverflowError, but if you add an output to the catch-block (not present in the example) you will see that only a single StackOverflowError is raised.

I also red that an error or exception thrown in a catch or finally block can replace the original one, but IMO the initial StackOverflowError has already been handled by the catch, once the finally block starts. In either case *something* should be visible in higher catch/finally blocks, but nothing shows up (also if you catch all Error or Throwable instead of just StackOverflowError).
Date User Action Args
2017-03-30 12:16:11stefan.richthofersetmessageid: <>
2017-03-30 12:16:11stefan.richthofersetrecipients: + stefan.richthofer, zyasoft, jeff.allen, jamesmudd
2017-03-30 12:16:11stefan.richthoferlinkissue2536 messages
2017-03-30 12:16:11stefan.richthofercreate