Tool/software:
Hello TI Community,
We are currently debugging an issue where two tasks encounter failures when using GateMutex for synchronization. However, we are uncertain whether both tasks are trying to access the same resource or another cause.
Issue Overview
• Two tasks are running concurrently, and we suspect that a GateMutex is not behaving as expected.
• We are seeing occasional failures where one task does not get the expected access.
• It is unclear whether both tasks are actually contending for the same resource or if the issue stems from another cause.
Observations & Questions
• Get_Reason makes a new copy of m_reason. Could this impact mutex behavior?
• Get_Reason is used in a strncpy operation. Would calling it before strncpy and passing its result help avoid potential race conditions?
• Are there known cases where GateMutex might fail in multi-task scenarios, even if tasks are accessing separate resources?
• What debugging strategies would help confirm whether both tasks are truly contending for the same resource?
We have attached logs and relevant code snippets that might help diagnose the issue.
Any insights or suggestions would be greatly appreciated!
P.F.A a doc with images to make more sense of our callstacks.
Thank you,
Mahima
GateMutex Failure.docx
