Linux command
heretek 命令
文本
复制后可按需替换文件名、目录或参数。
常用示例
Start heretek
heretek
Connect to a remote target
heretek -r [host:port]
Use a custom GDB binary
heretek --gdb-path [path/to/gdb]
Run in 32-bit mode
heretek --ptr-size 32
Execute GDB commands from a file
heretek -c [path/to/commands.gdb]
说明
heretek is a GDB TUI dashboard designed to seamlessly connect to remote targets even without a functioning gdbserver. It ships as a single statically-linked musl binary with no Python dependencies, making it ideal for embedded and minimal environments where vendors may ship GDB without Python support. heretek operates on systems with only gdb, nc (netcat), and mkfifo, bypassing common issues with broken gdbserver binaries. The dashboard displays registers, disassembly, stack, and memory in an organized TUI layout.
参数
- --gdb-path _PATH_
- Override gdb executable path
- -r, --remote _HOST:PORT_
- Connect to a netcat session for remote debugging
- --ptr-size _SIZE_
- Set pointer size mode (possible values: 32, 64, auto; default: auto)
- -c, --cmds _FILE_
- Execute GDB commands line-by-line from a file (lines starting with # are ignored)
- --log-path _PATH_
- Path to write log file (set RUST_LOG env variable to change log level)
- -h, --help
- Print help
- -V, --version
- Print version
FAQ
What is the heretek command used for?
heretek is a GDB TUI dashboard designed to seamlessly connect to remote targets even without a functioning gdbserver. It ships as a single statically-linked musl binary with no Python dependencies, making it ideal for embedded and minimal environments where vendors may ship GDB without Python support. heretek operates on systems with only gdb, nc (netcat), and mkfifo, bypassing common issues with broken gdbserver binaries. The dashboard displays registers, disassembly, stack, and memory in an organized TUI layout.
How do I run a basic heretek example?
Run `heretek` in a terminal, then adjust file names, paths, flags, or remote targets for your system.
What does --gdb-path _PATH_ do in heretek?
Override gdb executable path