Bug 57383 - Enhancents to call stack view
Enhancents to call stack view
Status: NEW
Product: debugger
Classification: Unclassified
Component: Code
4.x
All All
: P2 (vote)
: TBD
Assigned To: issues@debugger
issues@debugger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-03 06:23 UTC by _ sandipchitale
Modified: 2012-12-17 19:03 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ sandipchitale 2005-04-03 06:23:58 UTC
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)
Comment 2 Roman Ondruska 2006-06-16 13:09:00 UTC
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...
Comment 3 markiewb 2012-12-17 18:52:48 UTC
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost.
Comment 4 markiewb 2012-12-17 19:03:44 UTC
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.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo