Some scripts that can help pwntools open iTerm2 from the container
I don't like tmux when using pwntools to debug with GDB, so I made these scripts to use iTerm2 instead.
If you don't like tmux and prefer to use iTerm2, you come to the right place.
- When you
docker runthe container, add-v /tmp/iterm2-terminal:/tmp/iterm2-terminalto the options.
Something like this:
# original:
docker run -d --rm --name pwn-env --cap-add=SYS_PTRACE pwn-env
# add -v /tmp/iterm2-terminal:/tmp/iterm2-terminal :
docker run -d --rm --name pwn-env -v /tmp/iterm2-terminal:/tmp/iterm2-terminal --cap-add=SYS_PTRACE pwn-env-
In the container, download iterm2-terminal into your
$PATHand make it executable. -
In your script that uses pwntools, use:
from pwn import *
context.terminal = ['iterm2-terminal', '--option', '0']
...Note:
- There are 4 options:
--option 0: Open GDB in a new pane, split vertically--option 1: Open GDB in a new pane, split horizontally--option 2: Open GDB in a new tab--option 3: Open GDB in a new window
- In your macOS, download iterm2-terminal-docker into your
$PATHand make it executable, then run it with the container name and the shell you want to use in your iTerm2:
e.g.
iterm2-terminal-docker --name=pwn-env --shell=zsh- In the same session of the shell you just opened, if you run the script with
gdb.debug()orgdb.attach()in your container, it should open the GDB in iTerm2!
Feel free to open an issue if you have any questions or suggestions, also PRs are welcome!