I am using Ozone + J-Trace Pro on a target that is running ThreadX, and I am seeing some pretty crazy results on the Timeline view. Unfortunately, the only environment I know of with a ThreadX awareness plugin is IAR, which this project is not set up for. Image 1 shows what I am seeing at some places; note the deep stacking of the same function (a while loop waiting on a queue).
Is it expected that the stack unwinding for Timeline view will not be able to decipher the context switches?
Of course, it is possible that I am actually catching a major error of my own here ...
Images 2 and 3 show what a return look like in a case where the Timeline believes that it has returned to a function stacked upon itself, and the corresponding instruction trace.
Is it expected that the stack unwinding for Timeline view will not be able to decipher the context switches?
Of course, it is possible that I am actually catching a major error of my own here ...
Images 2 and 3 show what a return look like in a case where the Timeline believes that it has returned to a function stacked upon itself, and the corresponding instruction trace.