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.

Bug 40568 - [JDK1.5.0] Unexpected JDWP Error on 'step into'
Summary: [JDK1.5.0] Unexpected JDWP Error on 'step into'
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 3.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@debugger
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2004-02-27 14:50 UTC by Jan Chalupa
Modified: 2010-04-29 09:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample java source. (835 bytes, text/plain)
2004-02-27 14:51 UTC, Jan Chalupa
Details
Exception stack trace (1.70 KB, text/plain)
2004-02-27 14:53 UTC, Jan Chalupa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Chalupa 2004-02-27 14:50:08 UTC
[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.
Comment 1 Jan Chalupa 2004-02-27 14:51:17 UTC
Created attachment 13705 [details]
Sample java source.
Comment 2 Jan Chalupa 2004-02-27 14:53:10 UTC
Created attachment 13706 [details]
Exception stack trace
Comment 3 Maros Sandor 2004-02-27 15:17:26 UTC
Works fine here on b37, can you verify it?
Comment 4 Milan Kubec 2004-02-27 15:48:42 UTC
Cannot reproduce either on JDK 1.5.0 b40.
Comment 5 Jan Chalupa 2004-02-27 16:16:50 UTC
Still reproducible with b40. Sorry.
Comment 6 Maros Sandor 2004-02-27 17:23:37 UTC
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.
Comment 7 Maros Sandor 2004-03-02 13:58:22 UTC
This is now tracked in BugTraq as bug #4918173.
Comment 8 Quality Engineering 2010-04-29 09:16:47 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.