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: | Display static fields of the current frame's class | ||
|---|---|---|---|
| Product: | debugger | Reporter: | Marian Petras <mpetras> |
| Component: | Java | Assignee: | Martin Entlicher <mentlicher> |
| Status: | CLOSED FIXED | ||
| Severity: | blocker | CC: | bht |
| Priority: | P2 | Keywords: | UI |
| Version: | 3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 80090 | ||
| Bug Blocks: | 89617 | ||
The only work-around is to use watches or tooltip. I agree. If there is no "this" node, there should be "Static" node with the static fields (if there are some). It was proposed at nbdev, to add (for static as well as non static stack frames)
something like:
[-] Static
[+] class
[+] STATIC FIELD1
[+] STATIC FIELD2
...
I've started to work on this. Unfortunately this issue requires API enhancements - e.g. add a representation of a remote class into the JPDADebugger API. Since the class representation will be required also for other pusposes (e.g. heap-walking), it will take some time to design this... Fixed in trunk, by the commit of the fix of issue #80090. Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier. |
Some very simple ("Hello, world!"-like) applications do not create instances of classes at all and the application is completely run in a static context. When debugging, there is no easy way of watching values of the class's static field as the fields are not displayed in the "Local Variables" panel of the Debugger Window. The typical scenario is described in bug #28612. Implementation of this enhancement is quite important especially for novice Java programmers (writing such simple applications).