Allow debug to be ran without connecting gdb to allow other external …

[hal3002]

…debuggers

Pwntools Pull Request

Thanks for contributing to Pwntools! Take a moment to look at CONTRIBUTING.md to make sure you're familiar with Pwntools development.

Please provide a high-level explanation of what this pull request is for.

Testing

Pull Requests that introduce new code should try to add doctests for that code. See TESTING.md for more information.

Target Branch

Depending on what the PR is for, it needs to target a different branch.

You can always change the branch after you create the PR if it's against the wrong branch.

Branch	Type of PR
dev	New features, and enhancements
dev	Documentation fixes and new tests
stable	Bug fixes that affect the current stable branch
beta	Bug fixes that affect the current beta branch, but not stable
dev	Bug fixes for code that has never been released

Changelog

After creating your Pull Request, please add and push a commit that updates the changelog for the appropriate branch.
You can look at the existing changelog for examples of how to do this.

[peace-maker]

Which external debugger do you want to use? Maybe we can add proper wrappers too?

[hal3002]

Sorry for the delay. Just saw your comment. In this specific case, I have an GDB MCP server for my LLM models. While great for debugging standalone binaries for exploit development, I wanted a way to to allow the models debug generated exploits, shellcode, ROP shells, etc and it's a bit cumbersome to have test payloads spit out to run separately in a gdb session. I tried a couple of solutions but the easiest just seemed to be to use pwntools.debug normally and disable the GDB client piece to allow my MCP server to connect to the gdb server instance. The only downside I've run into is needing to run the initial gdb commands on the MCP side after connection but otherwise seemed to work pretty well.