Bug 81260 - Visual representation of execution path in editor
Visual representation of execution path in editor
Status: NEW
Product: debugger
Classification: Unclassified
Component: Code
6.x
PC Windows XP
: P2 (vote)
: 6.x
Assigned To: issues@debugger
issues@debugger
: UI
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-07-27 14:35 UTC by Jiri Kovalsky
Modified: 2006-10-23 15:46 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments
An example of execution path visualization (21.75 KB, image/png)
2006-07-27 14:36 UTC, Jiri Kovalsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2006-07-27 14:35:01 UTC
Description:
============
In my opinion it would be user appealing to have something like tagging lines
that were executed during debugging. Please take a look at the screenshot to get
what I mean. I think it could attract new users as such feature helps tracking
where the code ran.
Comment 1 Jiri Kovalsky 2006-07-27 14:36:47 UTC
Created attachment 32261 [details]
An example of execution path visualization
Comment 2 Martin Entlicher 2006-07-28 10:33:07 UTC
This looks nice and might be handy in situations when the code path is not
straightforward.
The visualization part needs to be consulted with UI team and the implementation
part with editor guys.
But our problem currently is, that when is the program just stopped somewhere,
we're not able to obtain the execution path from JDI. Therefore currently it can
works just during stepping through the code.
In order to have the execution path in all cases, we would have to log execution
of all statements via instrumentation. This is a complex task, but might be
considered in some future releases together with issue #38762.


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