|
|
|
Re: Debugger crashes with Torch and Mars [message #1736087 is a reply to message #1719040] |
Sat, 25 June 2016 10:34 |
Eclipse User |
|
|
|
I am seeing an almost identical behaviour. I am able to start the Lua program, and set a breakpoint, but step / continue is very unstable and often crashes the debugging session.
I spent several hours yesterday trying to work around this, and can confirm I see this in LDT stable release (1.3.1) w/ provided Eclipse, as well as when loading in the latest milestone (1.4M3) in Mars / Neon / Luna. I even went as far as compiling LDT from Git, and see the same behaviour.
One clue: If I start the program in debug mode and hide the variables tab, the debugger does *not* crash and I am able to step / inspect and use variable watches. If I switch to the variables tab, the instability resurfaces.
I am working with a Lua-Torch sample when seeing this:
https://github.com/Element-Research/rnn/blob/master/examples/simple-recurrence-network.lua
Stack trace is very similar to original post:
eclipse.buildId=4.6.0.I20160606-1100
java.version=1.8.0_91
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -data file:/home/benjii/rnn-neon/ -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
!ENTRY org.eclipse.dltk.debug 4 0 2016-06-24 19:15:07.777
!MESSAGE Unable to load variables
!STACK 0
org.eclipse.dltk.dbgp.exceptions.DbgpOpertionCanceledException: java.lang.InterruptedException: ResponsePacketWaiter already terminated
at org.eclipse.dltk.dbgp.internal.commands.DbgpDebuggingEngineCommunicator.communicate(DbgpDebuggingEngineCommunicator.java:100)
at org.eclipse.dltk.dbgp.DbgpBaseCommands.communicate(DbgpBaseCommands.java:43)
at org.eclipse.dltk.dbgp.internal.commands.DbgpContextCommands.getContextProperties(DbgpContextCommands.java:95)
at org.eclipse.dltk.dbgp.internal.commands.DbgpCoreCommands.getContextProperties(DbgpCoreCommands.java:200)
at org.eclipse.dltk.internal.debug.core.model.ScriptStackFrame.readVariables(ScriptStackFrame.java:59)
at org.eclipse.dltk.internal.debug.core.model.ScriptStackFrame.readAllVariables(ScriptStackFrame.java:130)
at org.eclipse.dltk.internal.debug.core.model.ScriptStackFrame.refreshVariables(ScriptStackFrame.java:425)
at org.eclipse.dltk.internal.debug.core.model.ScriptStackFrame.checkVariablesAvailable(ScriptStackFrame.java:405)
at org.eclipse.dltk.internal.debug.core.model.ScriptStackFrame.getVariables(ScriptStackFrame.java:472)
at org.eclipse.debug.internal.ui.model.elements.StackFrameContentProvider.getAllChildren(StackFrameContentProvider.java:53)
at org.eclipse.debug.internal.ui.model.elements.StackFrameContentProvider.getChildCount(StackFrameContentProvider.java:29)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildCount(ElementContentProvider.java:118)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$2.run(ElementContentProvider.java:67)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.InterruptedException: ResponsePacketWaiter already terminated
at org.eclipse.dltk.dbgp.internal.packets.DbgpResponcePacketWaiter.waitPacket(DbgpResponcePacketWaiter.java:44)
at org.eclipse.dltk.dbgp.internal.packets.DbgpPacketReceiver.getResponsePacket(DbgpPacketReceiver.java:61)
at org.eclipse.dltk.dbgp.internal.DbgpDebugingEngine.getResponsePacket(DbgpDebugingEngine.java:94)
at org.eclipse.dltk.dbgp.internal.commands.DbgpDebuggingEngineCommunicator.receiveResponse(DbgpDebuggingEngineCommunicator.java:44)
at org.eclipse.dltk.dbgp.internal.commands.DbgpDebuggingEngineCommunicator.communicate(DbgpDebuggingEngineCommunicator.java:69)
... 13 more
|
|
|
|
Powered by
FUDForum. Page generated in 0.01903 seconds