| Java VM crash & IOException debugging [message #148926] |
Tue, 16 March 2004 23:28  |
Eclipse User |
|
|
|
When attempting to debug my jar file with EclipseM7 the Java VM is
crashing and Eclipse displays an
error message indicating that an IOException occurred attempting to read
variable information from
the jar or something to that effect (it only flashes briefly). At the
point the IOException occurs it
appears to be trying to read either line number or variable debug info
from my jar file. This happens
on both Mac OS X running jdk1.4.2 and Windows running jdk1.4.1. The jar
file is apparently fine
otherwise as it executes perfectly as long I'm not debugging.
To the best of my recollection I've never seen this with any other 3.0
version. Has anyone else
encountered this?
|
|
|
|
| Re: Java VM crash & IOException debugging [message #149700 is a reply to message #148987] |
Thu, 18 March 2004 13:38  |
| Eclipse User |
|
|
|
Darin,
Here's the message I get. "com.sun.jdi.VMDisconnectedException: Got
IOException from Virtual
Machine occurred retrieving source name debug attribute."
Stack trace:
org.eclipse.debug.core.DebugException[5010]:
com.sun.jdi.VMDisconnectedException: Got
IOException from Virtual Machine
at
org.eclipse.jdi.internal.connect.PacketSendManager.sendPacke t(PacketSendManager.java:79)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:169)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:191)
at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.jav a:221)
at
org.eclipse.jdi.internal.ReferenceTypeImpl.getSourceName(Ref erenceTypeImpl.java:1563)
at
org.eclipse.jdi.internal.ReferenceTypeImpl.sourceName(Refere nceTypeImpl.java:1648)
at org.eclipse.jdi.internal.LocationImpl.sourceName(LocationImp l.java:170)
at org.eclipse.jdi.internal.LocationImpl.sourceName(LocationImp l.java:123)
at
org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getS ourceName(JDIStackFrame.java:839)
at
org.eclipse.jdt.launching.sourcelookup.JavaSourceLocator.get FullyQualfiedName(JavaSourceLocator.jav
a:274)
at
org.eclipse.jdt.launching.sourcelookup.JavaSourceLocator.get SourceElement(JavaSourceLocator.java:
242)
at
org.eclipse.jdt.debug.ui.JavaUISourceLocator.getSourceElemen t(JavaUISourceLocator.java:153)
at
org.eclipse.debug.internal.ui.views.launch.LaunchView.lookup EditorInput(LaunchView.java:710)
at
org.eclipse.debug.internal.ui.views.launch.LaunchView.openEd itorForStackFrame(LaunchView.java:
783)
at
org.eclipse.debug.internal.ui.views.launch.LaunchView.showEd itorForCurrentSelection(LaunchView.jav
a:689)
at
org.eclipse.debug.internal.ui.views.launch.LaunchView.select ionChanged(LaunchView.java:499)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:159)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:819)
at org.eclipse.core.runtime.Platform.run(Platform.java:493)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer .java:157)
at
org.eclipse.jface.viewers.StructuredViewer.updateSelection(S tructuredViewer.java:1310)
at
org.eclipse.jface.viewers.StructuredViewer.setSelection(Stru cturedViewer.java:1033)
at
org.eclipse.debug.internal.ui.views.launch.LaunchView.autoEx pand(LaunchView.java:1098)
at
org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHa ndler.doHandleSuspendThreadEvent(Lau
nchViewEventHandler.java:224)
at
org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHa ndler.doHandleSuspendEvent(LaunchVie
wEventHandler.java:184)
at
org.eclipse.debug.internal.ui.views.launch.LaunchViewEventHa ndler.doHandleDebugEvents(LaunchVie
wEventHandler.java:100)
at
org.eclipse.debug.internal.ui.views.AbstractDebugEventHandle r$1.run(AbstractDebugEventHandler.jav
a:70)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:3 5)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchr onizer.java:102)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.jav a:2094)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :1917)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1550)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1526)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:265)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:139)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:47)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:257)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:279)
at org.eclipse.core.launcher.Main.run(Main.java:742)
at org.eclipse.core.launcher.Main.main(Main.java:581)
What's totally frustrating about this is that I can debug my application
successfully at times and then
suddenly the exact same jar file, not even rebuilt with the same code, but
the exact same jar file will
starting failing with this error. Once it starts occurring I haven't
figured out a way to get it to stop
other than to rebuild everything, including my workspace, and even then it
sometimes continues to
occur. Argh!
Additional info:
java.version=1.4.2_03
java.vendor=Apple Computer, Inc.
BootLoader constants: OS=macosx, ARCH=ppc, WS=carbon, NL=en_US
Bob
Darin Wright wrote:
> Haven't seen this. Can you give us the strack trace? or file a bug with
> steps to reproduce?
> Darin
> "Bob" <gandalf@cal.net> wrote in message news:c38k5r$loh$1@eclipse.org...
> > When attempting to debug my jar file with EclipseM7 the Java VM is
> > crashing and Eclipse displays an
> > error message indicating that an IOException occurred attempting to read
> > variable information from
> > the jar or something to that effect (it only flashes briefly). At the
> > point the IOException occurs it
> > appears to be trying to read either line number or variable debug info
> > from my jar file. This happens
> > on both Mac OS X running jdk1.4.2 and Windows running jdk1.4.1. The jar
> > file is apparently fine
> > otherwise as it executes perfectly as long I'm not debugging.
> >
> > To the best of my recollection I've never seen this with any other 3.0
> > version. Has anyone else
> > encountered this?
> >
|
|
|
Powered by
FUDForum. Page generated in 0.03167 seconds
Home