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.
Build: NetBeans IDE 7.2 (Build 201207171143) VM: Java HotSpot(TM) Client VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24 OS: Windows 7 User Comments: ruol: error occurred while attaching Java Debugger (JPDA) via SocketAttach GUEST: Breakpoint just activated rhinoguy: Attaching the debugger to an existing applet. GUEST: trying to launch 3D java api ColorCube.java sample to test if applet can be run with netbeans and these jnlp launcher ruol: Error occured while attaching debugger via NetBeans attach menu item ... Java Debugger (JPDA) using Connector: SocketAttach (Attaches by socket to other VMs). GUEST: attaching the debugger Stacktrace: com.sun.jdi.InvocationException: Exception occurred in target VM at com.sun.tools.jdi.ClassTypeImpl.invokeMethod(ClassTypeImpl.java:246) at org.netbeans.modules.debugger.jpda.jdi.ClassTypeWrapper.invokeMethod(ClassTypeWrapper.java:280) at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener.initDebuggerRemoteService(VisualDebuggerListener.java:298) at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener.access$100(VisualDebuggerListener.java:122) at org.netbeans.modules.debugger.jpda.visual.VisualDebuggerListener$2.breakpointReached(VisualDebuggerListener.java:185) at org.netbeans.api.debugger.jpda.JPDABreakpoint.fireJPDABreakpointChange(JPDABreakpoint.java:293)
Created attachment 123269 [details] stacktrace
Integrated into 'main-golden', will be available in build *201210090002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/907fe0b98f13 User: mentlicher@netbeans.org Log: #217048: Log the target exception.
Created attachment 127745 [details] stacktrace Tried to debug an RMI server. Just installed 20121113 after uninstalling 1108 keeping configuration
Created attachment 127747 [details] stacktrace Seems debugger is unusable...
I believe, that debugger should continue fine after this exception occurs. My apologies for the problem in the code, which should log the actual target exception, that has occurred. After the fix of issue #222077 gets propagated into a dev build, please try this again. The real cause of this issue should be logged. Thanks.
Created attachment 127830 [details] stacktrace Starting debug session with 121115 and standard security manager installed.
Martin, I believe it does not, it seems to loose grip of the active process and the program continues without debugging or just sits on a breakpoint without beeing able to resume because the controls are inactivated.
Thanks to issue #222288 I know now what is the problem. Your SecurityManager does not allow to listen for all AWT events, which is used by visual debugging. We need to handle this gracefully and assure that the debugger can continue. I'm resolving this as a duplicate of issue #222288, since it contains the real cause after the logging was improved. *** This bug has been marked as a duplicate of bug 222288 ***