Klever

I will take care to identify who is responsible for this issue. When I implemented this everything worked as expected.

It turns out that sometimes everything works as expected but sometimes not. Actually when in addition to invoking of callbacks there are some actions in environment models like calling pre_probe() or switching to the interrupt context it is okay because of these action locations aren't moved to module source code. But when there is the only invocation of a callback this isn't the case - there is the only action which location refers to module source code.

Good news that nowadays error traces in addition to standard locations have so called original locations. So, when Bridge meets edges like the following (a first edge with a new action and various locations):

        {
            "action": 4,
            "enter": 9,
            "file": 2,
            "original file": 0,
            "original start line": 277,
            "source": "ldv_3_ret_default = my_init();",
            "source node": 32,
            "start line": 80,
            "target node": 33,
            "thread": 3
        }

For the attached example there is likely the only situation (specified above) where an error trace representation should change.

Implemented in feature_7997.

It works so I merged the branch to master in 37e1dc7.