Community
Participate
Working Groups
public class Test { public static void main(String[] args) { Thread.setDefaultUncaughtExceptionHandler(new UncaughtExceptionHandler() { @Override public void uncaughtException(Thread t, Throwable e) { e.printStackTrace(); } }); System.out.println("hello world"); } } Add a debug point in sysout statement and evaluate the following snippet. java.util.Arrays.asList(1).get(2) This will cause the current thread to handle the exception which was thrown from evaluating snippet. A application which handles uncaught exception and exit the VM will cause the application to stop due to a evaluation.
Tried the look at it more closer, but i cannot reproduce this bugs any more. I will check more its something due to the java version i was using.
Checking further it seems my application is not crashing due to default uncaught exception handler because the exception raised from the evaluation doesn’t get handled by DUEH or thread’s UEH. A interesting observation is that if you throw a exception in evaluation the current thread dies. This is not observed in Intellij. So may be this is the reason my application crashes.
From my tests i found out the current suspend thread doesn't crash if the evaluated method throws a exception. But if you evaluate something like throw new RuntimeException() this cause the suspended thread to die.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
