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.
Created attachment 32261 [details]
An example of execution path visualization
This looks nice and might be handy in situations when the code path is not
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.