Concurrency Debugging Laboratory
Replay observed thread events with vector clocks, examine mutex owners and wait cycles, and link findings to unordered memory accesses.
Application guideVerifying your session…
Using Concurrency Debugging Laboratory
Reconstruct concurrency problems from an instrumented execution trace.
Vector-clock replay · Mutex wait cycles · Race witnesses
- Inputs and working data
- Observed per-thread actions, memory locations, mutex ownership, spawn/join events, vector timestamps and cursor-linked findings.
- Working in the editor
- Trace import, replay slider and step buttons, ownership table, wait graph, happens-before inspector and findings.
- What can I produce?
- Cursor-specific replay JSON, retained race witness CSV and original normalized instrumented NDJSON.
- What are the limits?
- 64 threads, 10,000 events, up to 1,000 race witnesses retained. Models non-reentrant mutexes with explicit acquisition, release, thread finish and join.
- Example
- Import a shared-memory race and two-mutex wait cycle, compare vector clocks, replay across cycle formation and reopen the saved investigation.