Bug 562455

Summary:

Disabled Breakpoints still break.

Product:

[Eclipse Project] JDT

Reporter:

Ed Willink <ed>

Component:

Debug

Assignee:

JDT-Debug-Inbox <jdt-debug-inbox>

Status:

NEW ---

QA Contact:

Severity:

normal

Priority:

Version:

4.16

Target Milestone:

---

Hardware:

OS:

Windows 10

Whiteboard:

stalebug

Attachments:

Description	Flags
screenshot	none

Description Ed Willink

2020-04-24 04:11:07 EDT

4.15

While trying to develop the /org.eclipse.ocl.standalone.ecore.tests/.settings/org.eclipse.ocl.standalone.ecore.tests.launch to emulate the working Jenkins job...

A non-debug launch fails at the sixth test with an UnsupportedClassVersionError. Ok I've messed up, not everything is built with Java 5.

Trying a debug launch, it stops almost immediately at a UnsupportedClassVersionError. Ok, I have an UnsupportedClassVersionError and an Error breakpoint. Remove both.

Debug launch still stops at UnsupportedClassVersionError even though it is disabled, so I cannot proceed to the real problem. See attached screenshot.

Debug should proceed to the failure detected by non-debug.

Comment 1 Ed Willink

2020-04-24 04:15:48 EDT

Created attachment 282545 [details]
screenshot

Trying again

Comment 2 Eclipse Genie

2022-04-15 12:27:57 EDT

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 3 Eclipse Genie

2024-04-05 19:40:38 EDT

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.