Bug 534879

Summary:	Debug failed because of conditional breakpoint
Product:	[Eclipse Project] JDT	Reporter:	Siarhei Khamenka <supacrazypusher>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	4.8
Target Milestone:	---
Hardware:	PC
OS:	Windows 10
Whiteboard:	stalebug

Description Siarhei Khamenka

2018-05-18 13:10:55 EDT

What steps will reproduce the problem?
1.  Debug simple class with conditional breakpoint
2. 
3. 


-- Error Details --
Date: Fri May 18 20:07:13 MSK 2018
Message: An internal error occurred during: "JDI Event Dispatch".
Severity: Error
Product: Spring Tool Suite 3.9.4.201804120943-RELEASE (org.springsource.sts.ide)
Plugin: org.eclipse.core.jobs
Exception Stack Trace:
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/debug/eval/ast/engine/ASTEvaluationEngine (wrong name: org/eclipse/jdt/internal/debug/eval/ast/engine/ASTEvaluationEngine$AjcClosure1)
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.defineClass(ModuleClassLoader.java:273)
	at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.defineClass(ClasspathManager.java:632)
	at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findClassImpl(ClasspathManager.java:586)
	at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClassImpl(ClasspathManager.java:538)
	at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:525)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:325)
	at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:345)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:423)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
	at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at org.eclipse.jdt.debug.eval.EvaluationManager.newAstEvaluationEngine(EvaluationManager.java:73)
	at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.getEvaluationEngine(JDIDebugTarget.java:2795)
	at org.eclipse.jdt.internal.debug.core.breakpoints.ConditionalBreakpointHandler.getEvaluationEngine(ConditionalBreakpointHandler.java:282)
	at org.eclipse.jdt.internal.debug.core.breakpoints.ConditionalBreakpointHandler.breakpointHit_aroundBody0(ConditionalBreakpointHandler.java:207)
	at org.eclipse.jdt.internal.debug.core.breakpoints.ConditionalBreakpointHandler$AjcClosure1.run(ConditionalBreakpointHandler.java:1)
	at org.eclipse.contribution.jdt.debug.DebugHooksAspect.ajc$around$org_eclipse_contribution_jdt_debug_DebugHooksAspect$6$f39440eeproceed(DebugHooksAspect.aj:210)
	at org.eclipse.contribution.jdt.debug.DebugHooksAspect.ajc$around$org_eclipse_contribution_jdt_debug_DebugHooksAspect$6$f39440ee(DebugHooksAspect.aj:221)
	at org.eclipse.jdt.internal.debug.core.breakpoints.ConditionalBreakpointHandler.breakpointHit(ConditionalBreakpointHandler.java:185)
	at org.eclipse.jdt.internal.debug.core.model.JDIThread.handleSuspendForBreakpoint(JDIThread.java:1392)
	at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.suspend(JavaBreakpoint.java:407)
	at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleBreakpointEvent(JavaBreakpoint.java:396)
	at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.handleEvent(JavaBreakpoint.java:313)
	at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:186)
	at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:100)
	at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:250)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Comment 1 Eclipse Genie

2020-08-03 18:20:58 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.

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

Comment 2 Eclipse Genie

2023-02-15 11:55:44 EST

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.

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