Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 500137

Summary:	Breakpoints don't get highlighted if the debug view wasn't active before
Product:	[Eclipse Project] JDT	Reporter:	Elias Anderman <kosmosprime>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	trivial
Priority:	P3
Version:	4.6
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Elias Anderman

2016-08-23 10:50:50 EDT

If eclipse is set to not switch to the debug perspective and not open the debug view, when a breakpoint is hit but the debug view has not been open before, the breakpoint does work but eclipse does not highlight the line or allow you to inspect the values of variables by hovering the mouse cursor over them.
Switching to the debug perspective (which contains the debug view) or adding it fixes this, even if you switch back to the java view or close the debug view before starting the program. Restarting eclipse causes the bug to appear again.

Steps to reproduce:
1) In the preferences, under "Run/Debug", untick "Activate the debug view when a breakpoint is hit".
2) In the preferences, under "Run/Debug" -> "Launching", set "Launch in debug mode when workspace contains breakpoints" to "Never".
3) In the preferences, under "Run/Debug" -> "Perspectives", set "Open the associated perspective when launching" and "Open the associated perspective when an application suspends" to "Never".
4) Restart Eclipse.
5) Place a breakpoint in a location which gets executed (the program does not matter).
6) Launch the associated program.

This bug is by no means important as, when it occurs, simply switching to the debug view solves it. The error log view does not display any errors associated with the problem, so it likely has something to do with certain components not being initialized ahead of time.

Comment 1 Eclipse Genie

2020-04-22 05:55: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.