This repository was archived by the owner on Oct 16, 2020. It is now read-only.
This repository was archived by the owner on Oct 16, 2020. It is now read-only.
Gaps in call depths #22
Description
Below is a small part of the execution trace collected with blinky. I filtered all the execution out that have to do with thread 15.
['$$$', '67387', '15', '4875', '7', '910123336', '9393', '$enter$', 'NA\n']
['$$$', '67388', '15', '4875', '8', '1848651233', '9395', '$enter$', 'NA\n']
['$$$', '67389', '15', '4875', '8', '1848651233', '9397', '$enter$', 'NA\n']
['$$$', '67390', '15', '4876', '5', '1848651233', '9401', '$enter$', 'NA\n']
['$$$', '67391', '15', '4876', '6', '1848651233', '9397', '$enter$', 'NA\n']
['$$$', '67392', '15', '4876', '6', '1848651233', '9403', '$enter$', 'NA\n']
The call depth calculated by (blinky) is [7, 8, 8, 5, 6, 6]. So blinky seems to not instrument all the code causing gaps in the call depth. Is there away to make sure all the code is instrumented so we will make sure these gaps will not occur?
Or can it be that it is because of a different problem that we have gaps in our call depth? (I assume here that if a thread starts at a specific call depth it is not possible to go below that. So if our call depth starts at 7 then it shouldn't be able to go to 6 or lower.)