Bug 272681

Summary: [breakpoints] 'Exclude Exception Location' for breakpoint does not work for nested class
Product: [Eclipse Project] JDT Reporter: Markus Keller <markus.kell.r>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P3 CC: adrianp.quatinus, Michael_Rennie, sarika.sinha
Version: 3.5   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Markus Keller CLA 2009-04-17 08:17:12 EDT
I20090416-1053

- have this class:

package xy;
public class Try {
    private static final class Nested implements Runnable {
        public void run() {
            throw new IllegalArgumentException();
        }
    }

    public static void main(String[] args) {
        new Nested().run();
    }
}

- set an exception breakpoint for IllegalArgumentException
- debug
- when the breakpoint is hit, open the context menu on the suspended thread and choose Exclude Exception Location
=> restriction is added for xy.Try$Nested

- terminate and debug again
=> breakpoint is still hit

When I add a filter for xy.Try, the exception location is actually excluded.
Comment 1 Eclipse Genie CLA 2019-11-28 14:43:37 EST
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.
Comment 2 Sarika Sinha CLA 2019-12-09 01:47:27 EST
Still the same
Comment 3 Eclipse Genie CLA 2021-11-29 19:14:43 EST
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.
Comment 4 Eclipse Genie CLA 2023-11-21 09:49:37 EST
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.