-
Notifications
You must be signed in to change notification settings - Fork 41
Use the Windows API to demangle MSVC symbols on Windows #257
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
base: main
Are you sure you want to change the base?
Conversation
Thanks for the PR! While a cool idea in theory, I’d much prefer to try to improve the built-in demangler as much as possible. That way, all platforms benefit (including web / decomp.me). |
While I agree in principle, since MSVC mangling isn't documented, that may prove more challenging. Here are the test diff for this PR:
Most of these are alright IMO, though the fact that Microsoft's official API can't unmangle the What are your thoughts on this? |
The fact that there's already instances where it regresses is unfortunate! And the I just tried out the undname-rs library with
and it seems to work with the COM symbols, which is great! But it chokes on the same symbols that |
|
Sure, having the fallback seems good, but it looks like |
Right, that's a bug then... Your call, I suppose, whether we want to keep this not-quite-right behavior in. |
0cdde33
to
123b6a5
Compare
123b6a5
to
8487bef
Compare
This PR adds support to use the Windows API to demangle MSVC symbols on Windows.
Shouldn't affect other platforms.
Resolves #252