safe_dump_to causes a deadlock if signal is received when throwing an exception about stacktrace HOT 3 CLOSED

I was using quite old versions, but I don't think this was fixed in any newer releases of gcc or boost?

This doesn't really have much to do with boost, since the global lock in question comes from dl_iterate_phdr glibc function, which unwinders invoke when doing their stuff.

However, starting from glibc2.35 and gcc-12.3/llvm-16.0.0 this is no longer the case (at least it shouldn't be):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71744#c32
https://reviews.llvm.org/D130668

from stacktrace.

Adding more clarification in #156

As @itrofimow noted, there's not much we can do in Boost.Stacktrace.

from stacktrace.

Many thanks to all the participants! The docs are updated, changes will be in Boost 1.85

from stacktrace.