Closed zlojvavan closed 1 month ago
@zlojvavan there's some workaround in https://github.com/boostorg/stacktrace/issues/148. The issues seem to be about the same OS limitation
Does the workaround help?
@apolukhin not sure what is workaround there. I suppose it's just the order of static init/finit and there's not much end user can do cleanly if stacktrace lib internals finalized before his own code without author's intervening ;) sometimes I am forced to do such dirty tricks by replacing some static class instances with dynamically created ones and introducing memleak but it's better than crash during finit in my book
Could you provide a minimal reproducer?
Also note that implementation of the library changed in latest release. Does the issue still happen on new version of the library?
Updated the library in 1.85 to use the same aproach as the C++ standard library implementation. If the crash remains - it's a platform limitation
boost 1.81 from vcpkg on windows
"Copy Details" button in "Exception Thrown" window in VS 2022 as usually cannot open clipboard so please bear with me for bringing screenshot
tried to output stacktrace to stream during late destructor (apparently too late to idebug_) here's meaningful excerpt from the callstack from IDE