Upcoming features for #tracexec
#Exec backtrace and jump to parent
In next release, the #TUI will support gathering the exec #backtrace of any exec event, which will greatly simply debugging experience.
The exec backtrace shows the history of a specific event and indicates any ancestor spawns or directly tears itself down and becomes the new process.
Jump to parent is a lighter alternative to backtrace, where you just press `U` to jump to the parent exec evt.
I am very excited to share that #tracexec can now be used as a #debugger launcher.
It's usually not trivial or convenient to debug a program executed by a shell/python script(which can use pipes as stdio for the program).
The video shows how to use tracexec to launch #gdb to debug two simple programs piped together by a shell script.
Solves:
- https://stackoverflow.com/questions/5048112/use-gdb-to-debug-a-c-program-called-from-a-shell-script
- https://stackoverflow.com/questions/1456253/gdb-debugging-with-pipe
- https://stackoverflow.com/questions/65936457/debugging-a-specific-subprocess
kxxt