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.
| Summary: | [JDK1.5.0] Unexpected JDWP Error on 'step into' | ||
|---|---|---|---|
| Product: | debugger | Reporter: | Jan Chalupa <jchalupa> |
| Component: | Java | Assignee: | issues@debugger <issues> |
| Status: | CLOSED WONTFIX | ||
| Severity: | blocker | Keywords: | JDK_SPECIFIC |
| Priority: | P2 | ||
| Version: | 3.x | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
Sample java source.
Exception stack trace |
||
Created attachment 13705 [details]
Sample java source.
Created attachment 13706 [details]
Exception stack trace
Works fine here on b37, can you verify it? Cannot reproduce either on JDK 1.5.0 b40. Still reproducible with b40. Sorry. I can reproduce it on build 40. It happens when the Netbeans JPDA debugger tries to evaluate 'this' object reference in the current stack frame. It is some internal problem in JDI or below. This seems to be very specific to this test case. Slightly modified source code behaves differently. This is now tracked in BugTraq as bug #4918173. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |
[dev-200402261900; Sun JDK 1.5.0-beta b32c] I get exception stack traces dumped on console while trying to debug (via 'step into - F7') in a simple java class (see the first attachment). The exception stack trace starts with: com.sun.jdi.InternalException: Unexpected JDWP Error: 35 at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:47) at com.sun.tools.jdi.StackFrameImpl.thisObject(StackFrameImpl.java:126) at org.netbeans.modules.debugger.jpda.JPDACallStackFrame.getVariables(JPDACallStackFrame.java:220) (See the second attachment for a full stack trace.) Steps to reproduce: 1. Open the attached class source in the editor. 2. Place a breakpoint at line 35 -- 'Set s = ...' 3. Start the debugger via Alt-F5 4. After it stops at the breakpoint, start pressing F7 (confirm 'Step Out' / 'Don't Ask') 5. The first stack trace appears when the Name class constructor is stepped into for the first time. A series of stack traces is generated with each F7 after that. I was not able to reproduce the behavior with JDK 1.4.2_04.