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.
Steps to reproduce: 1. start debugging of some application (better non-ui) 2. press Pause button Result: if there is not set any breakpoint the application is paused but Local Variables and Call Stack views are empty. Application's sources opened in editor have not any debugger annotations (current pc). Than: 1. create breakpoint and let application stop on it 2. remove the breakpoint and press Continue 3. press Pause button Result: application is stopped in 'described' state - Local Variables and Call Stack contain particular data, editor contain current pc annotation.
Well, I agree that this is inconsistent. The breakpoint sets a current thread, which is then preserved until a different thread becomes current. Thus you always have the call stack and variables. We should probably unset the current thread on resume and perhaps try to choose somehow the current thread when the app is paused (if it's single-threaded it's easy).
Changing priority to P4 - not so common use-case, after the user sets the desired thread as current in Threads view, the other views (Local Vars and Call Stack) get populated.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team
v/c