OFFLINE DEVELOPER REPORT

WaitLens

Follow QNX IPC waits from a thread to its destination process.

pidin queries processes sequentially; this is not an atomic snapshot. Process-level cycle candidates do not prove deadlock. Destination threads and timing guarantees cannot be inferred. PID/TID reuse can affect comparisons.

Source labels: synthetic

cycle.txt

Input: synthetic

Input provenance is supplied by the caller, not independently verified.

3Processes
4Threads
2IPC waits
0Zombies

IPC waits · thread to process

Source PID:TIDStateDestination PIDCoverageSource line
200:1SEND300observed2
300:1REPLY200observed3

Process cycle candidates

200, 300

Multiple server threads can make process cycles harmless. Investigate with a kernel trace.

All parsed threads
PID:TIDNamePriorityStateBlockedSource line
200:1demo_client10rSEND3002
300:1demo_service10rREPLY2003
300:2demo_service10rRECEIVE14
400:1idle_service10rRECEIVE2005

Normalized input SHA-256: 8190d7910f301bc00fa4530afc783521d46bd951fef7902414b3775a9bc58b76

Read the evidence

SEND
The client is waiting for its message to be received.
REPLY
The message has been received; the client is waiting for a reply.
RECEIVE
The server is waiting on a local channel. Its blocked value is not a process edge.

Next: inspect the referenced source rows, check destination coverage, and recapture if a phase is missing. Use a kernel trace to investigate persistence or scheduling. Two samples do not measure wait duration.