Per https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1748597 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827015, the libunwind that ships with many systems is likely to be broken (the mentioned libunwind bug has not been fixed in any release of Ubuntu). Part of the problem is that the upstream libunwind hasn't released a version that includes these fixes, despite the core fix being merged a year ago

This impacts the ability to enable the CPU profiler in mongod; enabling --use-cpu-profiler causes MongoDB tests to randomly fail in 3.4 and up (this also impacts 3.2 and lower, but 3.4 made its tests more robust by detecting if mongod exits non-zero).

It'd probably be best if MongoDB shipped its own vendored copy of libunwind to mitigate this (with http://git.savannah.nongnu.org/cgit/libunwind.git/commit/?id=29483327bebaf6e0141a9bee8bb99552a63f1583 and http://git.savannah.nongnu.org/cgit/libunwind.git/commit/?id=4dea379ad982e946ee2ec561c7554faf34807b72 included).