-
Notifications
You must be signed in to change notification settings - Fork 29
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
Panic due to double SymInitializeW #37
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rust on Windows has to call
SymInitializeW
before generating a backtrace, and it doesn't callSymCleanup
afterward. IfAddressInfoObtainer
is then used, it callsSymInitializeW
again, which fails because it has already been called.Example code (set
RUSTBACKTRACE=1
):There is some background on how the backtrace crate handled a similar conflict here (also explains why Rust doesn't call
SymCleanup
).I think dlopen should:
SymInitializeW
but ignore its return valueSymCleanup
This behavior is awkward, but I think it's the only way to be compatible with how Rust uses
SymInitializeW
.I can submit a PR for this if it's welcome.
The text was updated successfully, but these errors were encountered: