mirror of
https://github.com/morluto/rea
synced 2026-10-25 22:08:11 -04:00
d32d9f2902
When cancellation or the deadline interrupted LLDB after it had published its bridge result, the tracer never read that result, so an explicit `target_process_created: false` (or `target_process_exit_observed: true`) was lost. The run kept a `native-target:unknown` marker that no cleanup retry could release, wedging the tracer for every later trace. Read the published result once LLDB's process group is stopped, even for an interrupted run, and apply the same target-gone proof in cleanup retry. Cancellation or timeout stays the primary outcome; a created target, a truncated result, or a missing PID alone stays unresolved. Fixes #5385 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>