Open
Description
If you've got some buggy C-level code, running in gdb can be very useful because it prints out a very detailed traceback, with full argument names and values. This could be achieved by something like gdb -return-child-result -batch -ex r -ex bt --args python -m pytest $PYTEST_ARGS
.
However, gdb doesn't work with distributed testing because they are separate process which gdb doesn't know anything about. There is the pytest-faulthandler
plugin which is handy but it produces a much more limited traceback with addresses only.
It would be nice if there were some way to run the child processes in gdb like this to automatically get these backtraces.