Show HN: Using C++23 <stacktrace> to get proper crash logs in C++ programs

This is my favorite macro: &quot;#define WIN32_LEAN_AND_MEAN&quot;<p>Why is it that even though Github or what ever has cutsie unicorns (or whatever it is) as error messages it feels fake and contrived while this define just feels like some random dude at MS naming it before going off to write Solitaire?

If you don&#x27;t care about exotica like async or signal safety, and just need to see the callstack from arbitray points, this can do the job without C++23:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;Ardour&#x2F;ardour&#x2F;blob&#x2F;master&#x2F;libs&#x2F;pbd&#x2F;stacktrace.cc">https:&#x2F;&#x2F;github.com&#x2F;Ardour&#x2F;ardour&#x2F;blob&#x2F;master&#x2F;libs&#x2F;pbd&#x2F;stackt...</a><p>(2 different implementations, one for POSIX-y systems with the execinfo.h header, and one for Windows)<p>The demange() function is elsewhere.

There are parts of C++ standard library that no one should ever use.<p>The examples are: regex, iostreams, locale...<p>My main concern - this can also become such a dead weight.

The code:<p><pre><code> &#x2F;&#x2F;a decent amount of this was copied&#x2F;modified from backward.cpp (https:&#x2F;&#x2F;github.com&#x2F;bombela&#x2F;backward-cpp) </code></pre> The license on the other side of that link:<p><pre><code> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</code></pre>

Reliable in-process crash reporting is exceptionally difficult.<p>The code must be fully async-safe, which means you cannot use &lt;stacktrace&gt;. You also cannot acquire mutexes, use any of the standard allocators, etc etc etc.

A question: Would it be possible to pass the stacktrace of the current thread to another, so that the stacktrace would be traceable across threadpools or worker threads?

Yet another library feature that will be used by nobody... While having a standard library is good, system programming presents tricky aspects like async-safety that are not adequately addressed. Therefore, considering the challenges involved, I believe it would be better to utilize existing libraries like crashpad to handle such scenarios.

I may be wrong, but as I recall it is good form to chain exception filter calls by making note of the return from `SetUnhandledExceptionFilter`. For example, if I want to use `&lt;stacktrace&gt;` and do copy-on-write using memory protection in the same program.

Maybe I am doing something wrong but the example code does not seem to work on VS 2022 (no output file after a div by zero or stack overflow crash).

This does not even remotely look to be signal safe to me?