When debugging with some of the other very popular tools like GDB all the threads are halted when a breakpoint is hit on any of the threads. Then threads can be switched and analyzed separately at the current state of execution.

When debugging with PDB only the thread that hits the breakpoint is halted. This makes it quite hard to debug multi-threaded programs (like IO based programs). Also it's annoying that the console output will be shown from other threads when the debugger is stopped.

I think it would be extremely helpful for many people to have PDB behave like GDB when debugging multithreaded applications: halt execution on all threads when breakpoint is hit and continue execution on all threads when execution is continued from the debugger.

This is a good idea.

I am currently leaning towards using a threading.Lock around `Pdb.interaction`, or `pdb.set_trace` with pdb++.

This would at least mitigate the issue where `pdb.set_trace` is used in some code that gets executed again, and two pdb instances would use the same input, e.g. when debugging web applications.

See also https://bugs.python.org/issue23163 for/about improving docs in this regard.