Closed mika-fischer closed 7 months ago
Try calling stacktrace before the exit for first time. Probably after such initialization the stacktrace would work after exit
Yes, that works, that's what I meant by
What helps is to format a stacktrace before exit() is called.
Still, it's a bit unfortunate that it just crashes otherwise...
I'm afraid that this is a Windows runtime limitation. I could do some initialization on program start, however this would make many other developers unhappy
Closing as 'wont fix'
I have a nodejs addon (basically a dll), and want to print a stacktrace under some circumstances using
to_string(stacktrace())
. If this happens after nodejs calls exit(), I get a crash. It does not make a difference whether I useBOOST_STACKTRACE_USE_WINDBG_CACHED
or not. What helps is to format a stacktrace before exit() is called.Maybe exit makes it impossible to load new dlls?