Community
Participate
Working Groups
Eclipse 3.0M4 If you run the following example, Eclipse will always break into the debugger when it reaches the throw statement. This differes from the previous behavior and gets very annoying if you use third party code that throws Errors and catches them later on. public class TestClass { public static void main(String[] args) { try { throw new Error(""); } catch (Error e) { } } }
Additional note: Eclipse doesn't break if "Suspend execution on compilation errors" is turned off, but this is obviously not a compilation error!
it's a side effect of the fix for bug 37760 JavaDebugOptionManager answers DONT_CARE, so the debugger suspends the thread.
A similar problem existed if you set "suspend on compilation..." false and "suspend on uncaught..." true, then debugged to a compilation error. It would suspend when it shouldn't have because the uncaught exception was returning DONT_CARE when it meant DONT_SUSPEND. Fixed in JavaDebugOptionsManager. Please verify, Luc.
Verified.
*** Bug 44894 has been marked as a duplicate of this bug. ***
*** Bug 44885 has been marked as a duplicate of this bug. ***
*** Bug 46252 has been marked as a duplicate of this bug. ***
*** Bug 46222 has been marked as a duplicate of this bug. ***
*** Bug 46879 has been marked as a duplicate of this bug. ***
*** Bug 47023 has been marked as a duplicate of this bug. ***