Klever

CPAchecker SMG again started to annotate error traces very intensively. This helps to track things influencing reported warnings, but also it can result in too long error traces. For instance, I attached the error trace produced for a simple test case. Usually we analyze error traces starting from the end. If your monitor is not huge, you can hardly find an eye for function init where the verification tool reported the bug. Even huge monitors will not help for some error traces for real programs.

I suggest to add a shortcut/button to open eyes after users will click on some lines within corresponding functions. Anton suggested to show even a new bar for this purpose like IDEs do, but it will not be great from my point of view. Any ideas are welcome.