Feature #7930
openPropose to show all actions of scenarios if it contains at least one note in error trace
0%
Description
It is inconvenient to analyze error traces if an error depends on callback order but some callbacks are hidden if no model functions are called there. Unwrapping of all scenarios will make the trace ugly, but to show completely the relevant ones is good choice I think. There is an example of the trace: http://ldvstore.intra.ispras.ru:8998/reports/unsafe/53435/
Here the trace looks like that mmc_blk_release callback is called by an environment model without any initialization, so user have to click at ldv_partially_ordered_scenario_1 eye to ensure that the assumption is wrong.
Updated by Evgeny Novikov over 7 years ago
- Status changed from New to Feedback
There is a pretty fine comment "Call an initialization callback. Invoke callback open from block_device_operations." showing that initialization was performed. So I don't understand what is missing at the first level.
In addition I don't understand what is proposed. If notes are present in error traces, corresponding paths are shown.
Updated by Ilja Zakharov over 7 years ago
I propose to show all actions for threads with already shown callbacks. For instance, it also helpful might be to see after callback invocation a hidden confirmation "Initialization has been successful.".