What problem does it solve? Diagnosing Python bugs in tests, scripts, and long-running processes is hard when tracebacks alone don't reveal why values are wrong, and interactive debugging often fails under test runners or in remote processes. ## Core Features & Use Cases - Local pdb debugging: Insert breakpoint() for an interactive REPL, launch scripts with python -m pdb, or run pytest with --pdb and --trace to trap failures. - Post-mortem inspection: Catch exceptions with pdb.post_mortem or python -m pdb -c continue to inspect locals at the crash site. - Remote debugging with debugpy and remote-pdb: Attach to already-running processes via DAP on port 5678, inject into a PID, or use remote-pdb with nc for a plain pdb prompt over TCP. - Use Case: A gateway subprocess misbehaves and cannot be restarted. Add remote_pdb.set_trace() in the suspect handler, trigger it, then connect with nc 127.0.0.1 4444 to inspect the live stack. ## Quick Start Add a breakpoint() call at the suspect line in my Python file and walk me through stepping through it in pdb to find why the value is wrong.
