Community
Participate
Working Groups
With i20040316, I am seeing this every time a build takes place (no other visible effect other than an entry in the log): !ENTRY org.eclipse.jdt.debug.ui 4 150 Mar 16, 2004 13:53:52.567 !MESSAGE Internal Error !STACK 1 org.eclipse.debug.core.DebugException: Breakpoint does not have an associated marker. at org.eclipse.debug.core.model.Breakpoint.ensureMarker(Breakpoint.java:258) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint.isCaught(JavaExceptionBreakpoint.java:206) at org.eclipse.jdt.internal.debug.core.breakpoints.JavaExceptionBreakpoint.setEnabled(JavaExceptionBreakpoint.java:184) at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.problemAdded(JavaDebugOptionsManager.java:289) at org.eclipse.jdt.internal.debug.ui.JavaDebugOptionsManager.resourceChanged(JavaDebugOptionsManager.java:175) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:255) at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:648) at org.eclipse.core.runtime.Platform.run(Platform.java:512) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:248) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:142) at org.eclipse.core.internal.events.AutoBuildJob.broadcastChanges(AutoBuildJob.java:71) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:138) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:168) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62) !SUBENTRY 1 org.eclipse.debug.core 4 5012 Mar 16, 2004 13:53:52.567 !MESSAGE Breakpoint does not have an associated marker.
*** Bug 55130 has been marked as a duplicate of this bug. ***
*** Bug 55131 has been marked as a duplicate of this bug. ***
*** Bug 55317 has been marked as a duplicate of this bug. ***
Fixed. Thank for the test case, Jim. The problem was a race between the creation of the compilation error and uncaught exception breakpoints, and the initialization of the breakpoint manager. The two breakpoint are created as non-persistant breakpoint, then during it's initialization, the breakpointmanager deletes all non-persistant breakpoint markers (cleaning from the previous session). The problem has always been there, but was hidden by a side effect of the fact that the breakpoint view (from the debug perspective), was always open before a Java launch in debug mode was perform. This is no more the default behavior. Added a static initializer in Breakpoint, so the BreakpointManager is initialized before any creation of breakpoints. Changes in org.eclipse.debug.core.Breakpoint.
Please verify Darin W. To reproduce a problem, lanch an Eclipse session with the breakpoints view not open, and launch a Java app in debug mode.
*** Bug 55396 has been marked as a duplicate of this bug. ***
Verified.
*** Bug 55470 has been marked as a duplicate of this bug. ***