We've previously observed the "timeout" phase of the etc/evergreen.yml project configuration getting stuck and hitting the 15-minute time limit. SERVER-27158 was a change to resmoke.py to reduce the sheer number of processes we'd have running towards the end of an Evergreen task; however, there remain cases where GDB itself is getting stuck. We should add additional logging in hang_analyzer.py to display the command and its arguments prior to it being run (e.g. by using GDB's echo command) so we have a better idea of where the issue is coming from in the future.

Note: GDB doesn't support a logging mode where it not only logs the output of the command but also the command itself. https://sourceware.org/bugzilla/show_bug.cgi?id=8822