This "improves" the current gdb.debug on mac for people using iTerm. Currently, gdb.debug returns an error because it can't figure out how to split the terminal and run the gdb process. Best option so far was to use tmux. This PR fixes it and allows to run gdb in the current window by splitting the terminal in 2.
Related to #2329
If/when this is merged, the next step would be to do the same for Vscode which would probably be useful to a lot of people.
This might need to be tested by someone else before merging. It works for me but my local setup is a bit messy as I do not have gdb/gdbserver installed, I'm running a docker container and pwntools (which runs on localhost) executes the gdb/gdbserver commands within the docker container. (If you want more details, I can write a quick script to show how to reproduce this setup)
This "improves" the current gdb.debug on mac for people using iTerm. Currently, gdb.debug returns an error because it can't figure out how to split the terminal and run the
gdb
process. Best option so far was to use tmux. This PR fixes it and allows to run gdb in the current window by splitting the terminal in 2. Related to #2329If/when this is merged, the next step would be to do the same for Vscode which would probably be useful to a lot of people.
This might need to be tested by someone else before merging. It works for me but my local setup is a bit messy as I do not have gdb/gdbserver installed, I'm running a docker container and pwntools (which runs on localhost) executes the gdb/gdbserver commands within the docker container. (If you want more details, I can write a quick script to show how to reproduce this setup)