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

Bug 322625

Summary: [breakpoints] Breakpoints aren't always shown in editor margin
Product: [Eclipse Project] JDT Reporter: Aaron Digulla <digulla>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: minor    
Priority: P3 CC: Michael_Rennie, pawel.1.piech, remy.suen
Version: 3.4   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Attachments:
Description Flags
Visual explanation of the bug none

Description Aaron Digulla CLA 2010-08-13 04:17:08 EDT 
Build Identifier: Since at least 3.4

When I double click to create a breakpoint in the editor margin (also by using Ctrl-Shift-B or the menu "Toggle Breakpoint"), the breakpoint gets added to the list in the debug view but sometimes, the circle in the margin is now drawn. Or it gets after a long time.

This doesn't always happen. From my gut feeling, I'd say that the circle appears often when Eclipse has been freshly started and they appear less often when Eclipse has been running for a long time or maybe when memory has been tight once.

There is nothing in the error log.

Reproducible: Sometimes

Steps to Reproduce:
1. Work with Eclipse for several days (without restarting)
2. Double click on the margin in a Java editor -> Sometimes, no breakpoint appears.
Comment 1 Aaron Digulla CLA 2010-08-13 04:25:31 EDT 
Created attachment 176525 [details]
Visual explanation of the bug
Comment 2 Aaron Digulla CLA 2010-08-13 04:51:11 EDT 
I just noticed that the cursor does change when I hover over the invisible breakpoint.

When I try to remove the breakpoint by double clicking or Ctrl+Shift+B or the menu, then nothing happens (except that the breakpoint gets selected in the BP View).
Comment 3 Remy Suen CLA 2010-08-13 06:27:42 EDT 
Do you have multiple "copies" of ActionServlet.java? I see that the 'J' icon in your editor is not filled in which would imply that that particular file is not on the build path.
Comment 4 Aaron Digulla CLA 2010-08-13 10:52:39 EDT 
Almost. The file is the source for a compiled class that's in a JAR (i.e. read-only, non-editable).

It seems that the IDE doesn't always pick that up as a "Java file that's on the classpath". Other editors have the "J" icon with the binary underlay.

I just checked: If I get the hollow "J", then breakpoints aren't visible. Also, jumping to the definition of the breakpoint doesn't work. But I can close the editor and open it again (for example with "Open Type"). Then, I get the correct editor type and the breakpoints start to work.

Breakpoints defined in the "hollow J" editor are visible in the list but they are broken: I can't jump to the definition and they don't show up in the correct editor. That means when I start to toggle them, I get two breakpoints and weird stuff like that.

Now where do the editors come from? I think that they are opened by stepping through the source and by clicking on stack frames. I'll keep an eye on that and post updates here.
Comment 5 Pawel Piech CLA 2011-06-08 09:57:03 EDT 
Is this still a problem in 3.7?
Comment 6 Michael Rennie CLA 2011-06-08 10:02:20 EDT 

*** This bug has been marked as a duplicate of bug 125768 ***