facebook

Debugging Normal Java after installing MyEclipse [Closed]

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse IDE
  2.  > 
  3. General Development
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #200317 Reply

    joshstaiger
    Member

    Hello,

    I seem to be having trouble debugging *any* Eclipse project at all after I install MyEclipse (even normal Java projects that I had been working on before outside of MyEclipse).

    When I hit debug, I am switched to the debug perspective and a debug process is launched, but then it just seems to hang there without stepping through my code at all. This happens whether or not I have set any breakpoints. When I try to terminate the debug process, I get a message of “not responding.”

    After uninstalling MyEclipse, this problem goes away, and debugging works fine again. I have tried installing MyEclipse a few times, each time with the same result.

    Any ideas? Is this a known problem and should I file a bug report?

    #200319

    support-michael
    Keymaster

    Josh,

    We need a little more info to get started. Please provide the info specified in the posting guidelines at the following URL and we’ll be happy to delve into your problem:
    http://www.myeclipseide.com/index.php?name=PNphpBB2&file=viewtopic&t=394

    Regards,

    Michael
    MyEclipse Support

    #200331

    joshstaiger
    Member

    Hello,

    Steps I have taken to reproduce this problem:

    Open up a normal Java Application project in the workspace.
    Set one or two breakpoints somewhere in code that I know should be executed by main.
    Select Run>Debug As Java Application for the .java file that has my main method

    The Debugger hangs without ever beginning to step through the code. It does this even if I do not set any breakpoints at all. When I try to terminate the debug process, the thread status goes to <not responding> in the debug window.

    Here are the details of my setup:

    Operating System: Windows XP

    Eclipse Version: 2.1.2
    Eclipse Build: 200311030802

    Eclipse was freshly installed for MyEclipse (I did a new install, but kept my old workspace)

    External Plugins: zTabNavigator (org.zclipse.tabnavigator v 1.1.0)

    > How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*

    Seven: pde.build, pde.core, pde.doc, pde.runtime, pde.source, pde.ui, and pde_2.1.0

    MyEclipse Version: 2.6.4

    JDK for Eclipse: j2sdk1.4.1_02
    JDK for App Server: j2sdk1.4.1_02

    App Server: Apache Tomcat 5.0.14

    I see the following in my log file:

    java.version=1.4.0_01-ea
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Command-line arguments: -os win32 -ws win32 -arch x86 -install file:C:/Program Files/eclipseForMyEclpise/
    !ENTRY org.eclipse.jdt.debug 4 120 Nov 26, 2003 08:45:35.525
    !MESSAGE Internal error logged from JDI Debug:
    !STACK 0
    com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine
    at org.eclipse.jdi.internal.connect.PacketSendManager.sendPacket(PacketSendManager.java:79)
    at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:169)
    at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191)
    at org.eclipse.jdi.internal.request.EventRequestImpl.enable(EventRequestImpl.java:222)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createClassPrepareRequest(JDIDebugTarget.java:960)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createClassPrepareRequest(JDIDebugTarget.java:927)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.createRequests(JavaBreakpoint.java:471)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.addToTarget(JavaBreakpoint.java:452)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.addToTarget(JavaLineBreakpoint.java:156)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.breakpointAdded(JDIDebugTarget.java:1043)
    at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.run(BreakpointManager.java:756)
    at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
    at org.eclipse.core.runtime.Platform.run(Platform.java:413)
    at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.notify(BreakpointManager.java:782)
    at org.eclipse.debug.internal.core.BreakpointManager.fireUpdate(BreakpointManager.java:684)
    at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoints(BreakpointManager.java:423)
    at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoint(BreakpointManager.java:400)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.register(JavaBreakpoint.java:177)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint$1.run(JavaLineBreakpoint.java:145)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.run(JavaBreakpoint.java:745)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.<init>(JavaLineBreakpoint.java:148)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.<init>(JavaLineBreakpoint.java:128)
    at org.eclipse.jdt.debug.core.JDIDebugModel.createLineBreakpoint(JDIDebugModel.java:253)
    at org.eclipse.jdt.internal.debug.ui.actions.ManageBreakpointRulerAction.addMarker(ManageBreakpointRulerAction.java:269)
    at org.eclipse.jdt.internal.debug.ui.actions.ManageBreakpointRulerAction.run(ManageBreakpointRulerAction.java:171)
    at org.eclipse.ui.texteditor.AbstractRulerActionDelegate.run(AbstractRulerActionDelegate.java:98)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.ui.internal.PluginAction.run(PluginAction.java:213)
    at org.eclipse.ui.texteditor.AbstractTextEditor$4.triggerAction(AbstractTextEditor.java:1767)
    at org.eclipse.ui.texteditor.AbstractTextEditor$4.mouseDoubleClick(AbstractTextEditor.java:1781)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:136)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)
    !ENTRY org.eclipse.jdt.debug 4 120 Nov 26, 2003 08:45:35.535
    !MESSAGE Internal error logged from JDI Debug:
    !STACK 0
    com.sun.jdi.VMDisconnectedException: Got IOException from Virtual Machine
    at org.eclipse.jdi.internal.connect.PacketSendManager.sendPacket(PacketSendManager.java:79)
    at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:169)
    at org.eclipse.jdi.internal.MirrorImpl.requestVM(MirrorImpl.java:191)
    at org.eclipse.jdi.internal.request.EventRequestImpl.enable(EventRequestImpl.java:222)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createClassPrepareRequest(JDIDebugTarget.java:960)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.createClassPrepareRequest(JDIDebugTarget.java:927)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.createRequests(JavaBreakpoint.java:471)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.addToTarget(JavaBreakpoint.java:452)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.addToTarget(JavaLineBreakpoint.java:156)
    at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.breakpointAdded(JDIDebugTarget.java:1043)
    at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.run(BreakpointManager.java:756)
    at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1006)
    at org.eclipse.core.runtime.Platform.run(Platform.java:413)
    at org.eclipse.debug.internal.core.BreakpointManager$BreakpointNotifier.notify(BreakpointManager.java:782)
    at org.eclipse.debug.internal.core.BreakpointManager.fireUpdate(BreakpointManager.java:684)
    at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoints(BreakpointManager.java:423)
    at org.eclipse.debug.internal.core.BreakpointManager.addBreakpoint(BreakpointManager.java:400)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.register(JavaBreakpoint.java:177)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint$1.run(JavaLineBreakpoint.java:145)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaBreakpoint.run(JavaBreakpoint.java:745)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.<init>(JavaLineBreakpoint.java:148)
    at org.eclipse.jdt.internal.debug.core.breakpoints.JavaLineBreakpoint.<init>(JavaLineBreakpoint.java:128)
    at org.eclipse.jdt.debug.core.JDIDebugModel.createLineBreakpoint(JDIDebugModel.java:253)
    at org.eclipse.jdt.internal.debug.ui.actions.ManageBreakpointRulerAction.addMarker(ManageBreakpointRulerAction.java:269)
    at org.eclipse.jdt.internal.debug.ui.actions.ManageBreakpointRulerAction.run(ManageBreakpointRulerAction.java:171)
    at org.eclipse.ui.texteditor.AbstractRulerActionDelegate.run(AbstractRulerActionDelegate.java:98)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
    at org.eclipse.ui.internal.PluginAction.run(PluginAction.java:213)
    at org.eclipse.ui.texteditor.AbstractTextEditor$4.triggerAction(AbstractTextEditor.java:1767)
    at org.eclipse.ui.texteditor.AbstractTextEditor$4.mouseDoubleClick(AbstractTextEditor.java:1781)
    at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:136)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2022)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1729)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
    at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
    at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
    at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
    at org.eclipse.core.launcher.Main.run(Main.java:747)
    at org.eclipse.core.launcher.Main.main(Main.java:583)

    #200336

    Scott Anderson
    Participant

    John,

    This issue is caused by a bug in the 1.4.0 JDK that you’re using to launch Eclipse. I know that you reported this:

    JDK for Eclipse: j2sdk1.4.1_02

    But the log clearly shows this:

    java.version=1.4.0_01-ea

    You should be able to see this if you open a command shell and type ‘java -version’. You’ll need to run Eclipse with a 1.4.1+ JDK for debugging to work properly. This is why you’re getting the VMDisconnectedException’s in the log.

    –Scott
    MyEclipse Support

    #200366

    joshstaiger
    Member

    Thank you. I have cleared out any lingering old jdks on my system and that has fixed the problem.

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Debugging Normal Java after installing MyEclipse [Closed]

You must be logged in to post in the forum log in