On some Windows binaries, there are a number of symbols that do not get properly demangled.
One example I see is "C:\Windows\ShellExperiences\ClockFlyoutExperience.dll."
The sample from Windows 10 (Version 10.0.18363) has 20,252 total symbols in bv.symbols. Of these, 7,796 are still mangled. Microsoft's undname.exe utility successfully demangles 6,394 of these.
Some example symbols:
?set@IsAttachable@XamlMember@InfoProvider@XamlTypeInfo@@UE$AAAX_N@Z
?get@?QIXamlType@Markup@Xaml@UI@Windows@@IsMarkupExtension@XamlUserType@InfoProvider@XamlTypeInfo@@UE$AAA_NXZ
?GetBindingConnector@?QIComponentConnector2@Markup@Xaml@UI@Windows@@MainPage@ClockFlyoutExperience@@UE$AAAPE$AAUIComponentConnector@2345@HPE$AAVObject@Platform@@@Z
On some Windows binaries, there are a number of symbols that do not get properly demangled.
One example I see is "C:\Windows\ShellExperiences\ClockFlyoutExperience.dll."
The sample from Windows 10 (Version 10.0.18363) has 20,252 total symbols in
bv.symbols. Of these, 7,796 are still mangled. Microsoft'sundname.exeutility successfully demangles 6,394 of these.Some example symbols: