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
Observed changes
Read left to right: before → after. Source lines refer to the original input files.
| PID:TID | Name before → after | Change | Before state / blocked | After state / blocked | Lines before → after |
|---|---|---|---|---|---|
| 101:1 | ./waitlens_probe → ./waitlens_probe | changed | SEND / 100 | REPLY / 100 | 3 → 3 |
send.txt
Input: synthetic
Input provenance is supplied by the caller, not independently verified.
IPC waits · thread to process
| Source PID:TID | State | Destination PID | Coverage | Source line |
|---|---|---|---|---|
| 101:1 | SEND | 100 | observed | 3 |
Process cycle candidates
None observed
Multiple server threads can make process cycles harmless. Investigate with a kernel trace.
All parsed threads
| PID:TID | Name | Priority | State | Blocked | Source line |
|---|---|---|---|---|---|
| 100:1 | ./waitlens_probe | 10r | NANOSLEEP | 2 | |
| 101:1 | ./waitlens_probe | 10r | SEND | 100 | 3 |
Normalized input SHA-256: 7b43dca32e364c14863f9cd897f381188504a279d3f0bc404f44e9e1551995cb
reply.txt
Input: synthetic
Input provenance is supplied by the caller, not independently verified.
IPC waits · thread to process
| Source PID:TID | State | Destination PID | Coverage | Source line |
|---|---|---|---|---|
| 101:1 | REPLY | 100 | observed | 3 |
Process cycle candidates
None observed
Multiple server threads can make process cycles harmless. Investigate with a kernel trace.
All parsed threads
| PID:TID | Name | Priority | State | Blocked | Source line |
|---|---|---|---|---|---|
| 100:1 | ./waitlens_probe | 10r | NANOSLEEP | 2 | |
| 101:1 | ./waitlens_probe | 10r | REPLY | 100 | 3 |
Normalized input SHA-256: eca51830e1ee9499b54923c8ecbfd760ef018c0784d8e840d1c9c4a9b161f036
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.