Bug 538802 - Control flow not updating to reflect sched_switch event (should change to orange - wait for CPU).
Summary: Control flow not updating to reflect sched_switch event (should change to ora...
Status: UNCONFIRMED
Alias: None
Product: Tracecompass
Classification: Tools
Component: CTF (show other bugs)
Version: 4.0.0   Edit
Hardware: PC Linux
: P3 normal
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Project Inbox CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-07 12:02 EDT by Jason Puncher CLA
Modified: 2019-04-27 19:38 EDT (History)
2 users (show)

See Also:


Attachments
trace-compass-snapshot (123.61 KB, image/png)
2018-09-07 12:02 EDT, Jason Puncher CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Puncher CLA 2018-09-07 12:02:45 EDT
Created attachment 275746 [details]
trace-compass-snapshot

We've developed at tool that captures a trace from a card running VxWorks, and translated the system events into commands that would be understood by TraceCompass (in CTF format).

For the most part everything is working.  However, we occasionally run into issues where a task is scheduled out, but the green bar in the control flow stays green (whereas it should be waiting for the CPU - orange).

In this case, the resource window does show that the task (tAtrcS) has been swapped out and that only the new task (L3PP) is running.
Comment 1 Patrick Tasse CLA 2018-09-07 13:02:14 EDT
In the screenshot, the event table shows that for this sched_switch, prev_tid=0. Shouldn't it be prev_tid=785059840 (tAtrcS)?

A tid of 0 is interpreted as the swapper process. This might be the reason why the tAtrcS state is not being changed.
Comment 2 Matthew Khouzam CLA 2019-04-27 19:36:36 EDT
Hi Jason, I am looking at your pic, your TIDs are enormous. maybe we are experiencing a wrap-around. I think our max size is 16 bits, I need to confirm.

Any way you can send an anonymized trace?
Comment 3 Matthew Khouzam CLA 2019-04-27 19:38:06 EDT
I think Patrick hit it on the head though, your prev_tid field needed to be 785059840.