The mongodb-dump-locks command calls LockManager::dump() on the globalLockManager instance, which attempts to write the LockManager's lock state information to the mongod's stdout pipe via calls to log(). If another thread is already in the midst of logging to the console, then calling the LockManager::dump() function will block upon constructing another Console instance.

We should either (a) depend only on mongodb-show-locks and stop calling the mongodb-dump-locks command in hang_analyzer.py, or (b) add a version of LockManager::dump() that returns a string and doesn't attempt to call the log() function so that GDB can print the lock state messages itself.