You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
For debugging JaCoCo integrations it would be useful to have an read-only class file editor to display JaCoCo analysis data:
Tab: Info
VM class name
Source file name
class id
total method count
total instruction count
total branches count
total complexity count
total lines count
Tab: Methods
Table-Tree listing all methods
Columns: VM method descriptor, total instructions, total branches, total complexity, total lines
Each method be expanded to list its lines
Column data shown per line: Line Number, total instructions, total branches
Tab: Lines
Table listing all lines
Columns: Line number, total instructions, total branches
Tooltip per row: vm Method descriptors contributing to this line
brock_j
To help with debugging the result of instrumentations it might be a good idea to have a view or editor that can show the original bytecode and instrumented bytecode side by side.
I have implemented a prototype of this using the built in eclipse disassembler and compare viewers, but i think the result is a bit 'noisy' to be useful due to changes to program counters introduced by instrumenting. Will attach a screenshot to demonstrate
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For debugging JaCoCo integrations it would be useful to have an read-only class file editor to display JaCoCo analysis data:
brock_j
To help with debugging the result of instrumentations it might be a good idea to have a view or editor that can show the original bytecode and instrumented bytecode side by side.
I have implemented a prototype of this using the built in eclipse disassembler and compare viewers, but i think the result is a bit 'noisy' to be useful due to changes to program counters introduced by instrumenting. Will attach a screenshot to demonstrate
The text was updated successfully, but these errors were encountered: