Files
reverse-engineering-anything/src/rizin
morluto 6510264bfd feat(debuggers): name why a stopped GDB or Rizin session accepts no commands (#11185)
* feat(debuggers): name why a stopped GDB or Rizin session accepts no commands

* fix(debuggers): keep the stop code on startup protocol failures

* chore(mcp): record the debugger status schemas' closed_reason_code in the advertised summary

* fix(debuggers): name the stop code on a timed-out command whose cleanup is incomplete

A GDB console command that reached its deadline while its owned process could not be confirmed stopped returned a capability error without details.diagnostics.session_stop, although the session had recorded command-deadline. Rizin's retained cleanup failure after a timed-out or exited command omitted it the same way. Both now carry the session's stop code, read from the recorded stop (GDB) and the session's stop-reason owner (Rizin). The unreachable second command-deadline assignment in the GDB timer is removed.
2026-11-16 03:59:05 +08:00
..