Dynamic builds being the default in our testing has left us in the unfortunate position that barring some investigation and insight, coredumps can no longer be freely inspected. The standard pretty printers that get installed for (certain) strings will peg the CPU and consume all the memory when inspecting a mongod process.

The problematic invocation is gdb.lookup_type for std::_cxx11::string and std::_cxx11::wstring.

The ideal outcome of this ticket is two-fold:

• Create a custom pretty printer for std::string objects that avoid calling gdb.lookup_type on the aforementioned problematic types.
• Create a (literal) patch snippet that can be applied to the mongodb toolchain libstdcxx/v6/printers.py file which disables the problematic printers registered here. Add this snippet into buildscripts/setup_spawnhost_coredump.