-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Diff view #22
Comments
Thanks for the request! Coloring blocks differently based on their origin/set is something I've considered, but there are some complexities to doing 'attribution' on composed coverage sets. This may require some pretty fundamental changes to how Lighthouse manages coverage internally, so I have been putting it off. Since you're not the first to ask for this, I think this is something that will come sooner than later (maybe v0.8?) |
As for a 'Diff Overview', I honestly don't see this in the immediate future. I agree that there is value in it, but I don't think it is worth the costs (time, motivation) for me to pursue right now. |
I personally think something like similarity has a lot of value in finding what went wrong or what changed (in Fuzzing or RE). |
It would be good to have a feature like a Diff mode where you compare two composers output.
Nodes that appear in only one of can be colored yellow and those that appear in both blue .
Also there can be a column in Diff Overview which shows similarity and each row should be colored based on similarity.
The definition of similarity is a bit tricky it's good to have multiple algorithms for it.
I remember BinDiff had good diff views you can refer to.
BTW, This is a great plugin, I was looking for this for a long time. Thanks :)
The text was updated successfully, but these errors were encountered: