Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 328134 - [breakpoints] Debugger does not stop if breakpoint set on class as receiver
Summary: [breakpoints] Debugger does not stop if breakpoint set on class as receiver
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-19 10:32 EDT by Dani Megert CLA
Modified: 2020-04-20 06:34 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2010-10-19 10:32:23 EDT
3.6 but I think this never worked.

Test Case:
1. paste this into Package Explorer:
public class C {
	public static void main(String[] args) {
		Object c= new C();
		/* breakpoint 1 */ c
		.
		hashCode();
		/* breakpoint 2 */ C
		.
		foo();
	}
	private static int foo() {return 0;}
}

2. add breakpoints as commented in the source
3. start debugger
==> only breaks on first breakpoint.
Comment 1 Michael Rennie CLA 2013-12-06 14:34:29 EST
(In reply to Dani Megert from comment #0)

> ==> only breaks on first breakpoint.

The keen eye will notice that the second breakpoint does not get installed (does not have the 'check' on it in the editor or the view). If I had to guess (since I have debugged through it) I would say that the line the second bp is on does translate to a runnable line in the classfile, so it is ignored (not installed).
Comment 2 Eclipse Genie CLA 2020-04-20 06:34:00 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.