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 164201 - attached debugger is stepping into wrong jdk classes
Summary: attached debugger is stepping into wrong jdk classes
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Entlicher
Depends on:
Reported: 2009-04-30 13:55 UTC by Filip Zamboj
Modified: 2010-07-30 11:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

project (47.39 KB, application/x-compressed)
2009-04-30 13:58 UTC, Filip Zamboj

Note You need to log in before you can comment on or make changes to this bug.
Description Filip Zamboj 2009-04-30 13:55:46 UTC
Product Version: NetBeans IDE 6.7 Beta (Build 200904220001)
java version "1.6.0_14-ea"
Java(TM) SE Runtime Environment (build 1.6.0_14-ea-b03)
Java HotSpot(TM) Client VM (build 14.0-b12, mixed mode, sharing)

Steps to reproduce: 
1. run netbeans 
2. set two jdk platforms (1.6.0_14-ea-b03&1.5.0_17) in my case 
3. open attached project and set JDK6 for it 
4. disable stepping through jdk6 sources in Variables -> Remote Attach View 
5. attach from console (project attached to this issue). 
java -Xdebug -Xrunjdwp:transport=dt_socket,address=localhost:1234,server=y examples.advanced.MemoryView
6. attach debugger to localhost from netbeans 
7. verify that jdk6 sources are disabled <- WORKS OK 
8. see there are jdk5 sources present in source root <- WHY? and why are enabled? 
9. step into jdk class 
result: debugger steps into jdk 1.5.0_17 
expected result: it doesn't step to any jdk class
Comment 1 Filip Zamboj 2009-04-30 13:58:45 UTC
Created attachment 81309 [details]
Comment 2 Filip Zamboj 2009-04-30 13:59:21 UTC
btw - this was Vista. Should I try to reproduce on Linux? 
Comment 3 Martin Entlicher 2009-04-30 15:54:16 UTC
Well, the debugger does not try to compare the version of JDK the debuggee is running on with the version of JDK sources
that are available in Sources window.

This is why initially you have all JDK sources enabled and it's expected that you keep enabled only the one source root
that corresponds to the version of JDK that you're debugging.

I've heard complaints about this in past as well, so we should try to make it more comfortable.
We can use the specification version to compare the JDKs and select the correct (or closest) one.