On Windows, there's no way to figure out what happened unless we have a stack trace. Running gdb is too complicated for the average user, so boost::stacktrace support was added. It's however not enabled yet, so this bug serves as a reminder to do so.
First step taken: b409dfdc01ed36b54f5b8a70b3738146a26bf37e enables stacktrace support on some Linux distributions (e.g. Debian). Gentoo fails because of libstacktrace issues: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66570