Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[win32] crash with 0xC000000D in dll after exit() was called #148

Closed
mika-fischer opened this issue Nov 27, 2023 · 3 comments
Closed

[win32] crash with 0xC000000D in dll after exit() was called #148

mika-fischer opened this issue Nov 27, 2023 · 3 comments

Comments

@mika-fischer
Copy link

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 use BOOST_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?

2023-11-27_14h51_24 2023-11-27_14h51_14 2023-11-27_14h51_18
@apolukhin
Copy link
Member

Try calling stacktrace before the exit for first time. Probably after such initialization the stacktrace would work after exit

@mika-fischer
Copy link
Author

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...

@apolukhin
Copy link
Member

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'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants