Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332247 - Stack frame labels empty, unable to use debugger
Summary: Stack frame labels empty, unable to use debugger
Status: CLOSED DUPLICATE of bug 301412
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-09 15:23 EST by Samantha Chan CLA
Modified: 2010-12-10 09:41 EST (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 Samantha Chan CLA 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 CLA 2010-12-10 00:32:18 EST 
Looks like a dup of bug 301412
Comment 2 Samantha Chan CLA 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 CLA 2010-12-10 09:41:19 EST 

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