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.
I would like to see the following info in the call stack view: Current Thread, Thread Group ( I know one can see all threads in the Threads window). Here I am talking about showing the thread associated with the current stack. The method names should be shown first. The declaring class name should be shown after the method name or possibly in a different column so that the table could be sorted on declaring class name. There should be an option to show complete method signature including return type. There should be an option to show fully qualified class names everywhere class names are shown i.e. declaring class, method parameters and return type. It should be possible to jump to those classes when possible. The package name of the declaring class could be shown in a different column once again allowing sorting on that column. There should be an option to show more info about the location file. This info could be split into three columns, file name, package path, classpath folder or jar file (when known). There should be a separate column for the stack frame depth starting with top of the stack frame as the 1st. This is helpful when the view is sorted on other columns. Overall here are the columns I would like to see: 1. Stack Frame Depth 2. Method name (optionally full signature) 3. declaring class 4. declaring class package 5. file name 6. file package path (could be same as 4) 7. classpath entry - directory or jar or zip file (when known)
Check out: http://blogs.sun.com/roller/page/scblog?entry=jpda_java_debugger_call_stack
Sandip, thanks for the ideas, we will consider them for promo-H. Let me note that we have no options for debugger now, but this may change in the future...
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost.
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost. This time the target milestone is really set.