Community
Participate
Working Groups
20031010 The breakpoinm view is empty, that means no breakpoint is set, but the debugger still stops at uncaught execptions. Example: In a Junit tests that fails: Thread [main] (Suspended (exception AssertionFailedError)) Assert.fail(String) line: 47 Assert.assertTrue(String, boolean) line: 20 ReorgQuickFixTest(QuickFixTest).collectCorrections(ICompilationUnit, ...
Do you have the option to "suspend on uncaught" exceptions on (in the Java debug preferences?)
*** This bug has been marked as a duplicate of 44759 ***
ok, that was it, thanks. I wasn't aware of this preference. Would it make sense to have corresponding entries in the breakpoints view? E.g. an entry: 'Uncaught excpetions' and 'Compilation errors' that maybe can only be checked off but not deleted? My thinking that lead to this bug report was that, 'if the breakpoint view is empty, why would it stop at all!" Ok to close otherwise.
(Duplicate notation was wrong in this case). Will re-open as a feature request.
Deferred
*** Bug 103018 has been marked as a duplicate of this bug. ***
*** Bug 123321 has been marked as a duplicate of this bug. ***
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.