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

Bug 332247

Summary:	Stack frame labels empty, unable to use debugger
Product:	[Eclipse Project] JDT	Reporter:	Samantha Chan <chanskw>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	major
Priority:	P3	CC:	darin.eclipse, Michael_Rennie
Version:	3.6.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Samantha Chan

2010-12-09 15:23:34 EST

eclipse.buildId=M20100909-0800
java.fullversion=JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr6-20090923_42924 (JIT enabled, AOT enabled)
J9VM - 20090923_042924
JIT  - r9_20090902_1330ifx1
GC   - 20090817_AA
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Framework arguments:  -vm /home/chanskw/ibmjvm-15/ibm-java2-i386-50/bin/java
Command-line arguments:  -os linux -ws gtk -arch x86 -vm /home/chanskw/ibmjvm-15/ibm-java2-i386-50/bin/java


Not sure if this is a JVM problem, or Eclipse bug.

I suspend the thread (or the entire JVMM) and all the stackframe labels are empty.  Variables can be seen.  Clicking on the stackframes will take you to the source location.

Found these in the error log:

com.sun.jdi.ObjectCollectedException
	at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler(MirrorImpl.java:241)
	at org.eclipse.jdi.internal.ReferenceTypeImpl.getSourceDebugExtension(ReferenceTypeImpl.java:1547)
	at org.eclipse.jdi.internal.ReferenceTypeImpl.isSourceDebugExtensionAvailable(ReferenceTypeImpl.java:1610)
	at org.eclipse.jdi.internal.ReferenceTypeImpl.defaultStratum(ReferenceTypeImpl.java:1493)
	at org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.bind(JDIStackFrame.java:159)
	at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames(JDIThread.java:539)
	at org.eclipse.jdt.internal.debug.core.model.JDIThread.computeStackFrames(JDIThread.java:584)
	at org.eclipse.jdt.internal.debug.core.model.JDIThread.getTopStackFrame(JDIThread.java:1054)
	at org.eclipse.debug.internal.ui.contexts.LaunchSuspendTrigger.notifySuspend(LaunchSuspendTrigger.java:109)
	at org.eclipse.debug.internal.ui.contexts.LaunchSuspendTrigger.handleDebugEvents(LaunchSuspendTrigger.java:91)
	at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java:1089)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java:1123)
	at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:390)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Darin Wright

2010-12-10 00:32:18 EST

Looks like a dup of bug 301412

Comment 2 Samantha Chan

2010-12-10 08:33:45 EST

(In reply to comment #1)
> Looks like a dup of bug 301412

looks like it.
In my environment, the workbench is on latest IBM 1.5 JVM.  The target JVM is latest 1.6 JVM. 

I switched the workbench to the latest IBM 1.6 JVM, and that got around the problem.

Comment 3 Michael Rennie

2010-12-10 09:41:19 EST


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