This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
running a J2SE app in debug mode: com.sun.jdi.InternalException: Unexpected JDWP Error: 13 at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:47) at com.sun.tools.jdi.ThreadReferenceImpl.currentContendedMonitor(ThreadReferenceImpl.java:433) at org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl.getContendedMonitor(JPDAThreadImpl.java:392) at org.netbeans.modules.debugger.jpda.ui.models.MonitorModel.getChildren(MonitorModel.java:107) at org.netbeans.spi.viewmodel.Models$CompoundTreeModel.getChildren(Models.java:568) at org.netbeans.spi.viewmodel.Models$CompoundModel.getChildren(Models.java:2193) at org.netbeans.modules.viewmodel.TreeModelNode$TreeModelChildren.evaluateLazily(TreeModelNode.java:508) at org.netbeans.modules.viewmodel.TreeModelNode$LazyEvaluator.run(TreeModelNode.java:893) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:499) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932)
JDWP Error: 13 means THREAD_NOT_SUSPENDED - "If the specified thread has not been suspended by an event." I do not get this - JDWP protocol does not mention this error for CurrentContendedMonitor Command: http://java.sun.com/javase/6/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_ThreadReference_CurrentContendedMonitor Nor does it mention that the thread should be suspended by an event! JDI on the other hand requires the thread to be suspended, but not by an event: http://java.sun.com/javase/6/docs/jdk/api/jpda/jdi/com/sun/jdi/ThreadReference.html#currentContendedMonitor() Will try to investigate how it actually behaves... Anyway, it is a bug in JDI/JDWP.
Any com.sun.jdi.InternalException is a bug in JDI, it should never be thrown into (API) client code. If the problem was on NB debugger side, IncompatibleThreadStateException would be thrown. Unfortunately, without a repro-case this is not likely to be fixed on JDI side. Anyway, I am keeping this issue as P4 not to lost the stack trace.
IMHO this was fixed in 6.5, if it was caused by a bad synchronization in NB debugger. If it's a JDI bug, it can not be fixed in NB anyway. Please reopen if the bug reappears, with concrete steps to reproduce.
ok