Bug 329951 - Removing breakpoint during execution causes exceptions
Summary: Removing breakpoint during execution causes exceptions
Status: CLOSED DUPLICATE of bug 354784
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-10 17:14 EST by Missing name CLA
Modified: 2011-08-22 10:16 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Missing name CLA 2010-11-10 17:14:17 EST 
Build Identifier: 

I've got two exceptions when I tried to remove a (possibly conditional) breakpoint during the time the code was run in the debugger.

Here are stack traces:

1:

org.eclipse.debug.core.DebugException: Breakpoint does not have an associated marker.
	at org.eclipse.debug.core.model.Breakpoint.ensureMarker(Breakpoint.java:268)
	at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.getSuspendPolicy(JavaBreakpoint.java:911)
	at org.eclipse.jdt.internal.debug.core.model.JDIThread.completeBreakpointHandling(JDIThread.java:1157)
	at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.eventSetComplete(JavaBreakpoint.java:311)
	at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:204)
	at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:104)
	at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:250)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

2:

org.eclipse.debug.core.DebugException: Breakpoint does not have an associated marker.
at org.eclipse.debug.core.model.Breakpoint.ensureMarker(Breakpoint.java:268)
at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.isConditionSuspendOnTrue(JavaLineBreakpoint.java:533)
at org.eclipse.jdt.internal.debug.core.breakpoints.ConditionalBreakpointHandler$EvaluationListener.determineVote(ConditionalBreakpointHandler.java:112)
at org.eclipse.jdt.internal.debug.core.breakpoints.ConditionalBreakpointHandler$EvaluationListener.evaluationComplete(ConditionalBreakpointHandler.java:81)
at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine$EvalRunnable.evaluationFinished(ASTEvaluationEngine.java:552)
at org.eclipse.jdt.internal.debug.eval.ast.engine.ASTEvaluationEngine$EvalRunnable.run(ASTEvaluationEngine.java:547)
at org.eclipse.jdt.internal.debug.core.model.JDIThread$ThreadJob.run(JDIThread.java:2756)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Reproducible: Didn't try
Comment 1 Michael Rennie CLA 2011-08-22 10:16:23 EDT 
marking as dupe of bug 354784 as there is more discussion there and the underlying problem is the same: we are trying to access the marker for a breakpoint that no longer exists (via Breakpoint#ensureMarker)

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