Demangler Plugins

[plafosse]

Provide a generic API for users to add their own name demanglers to be run during analysis. This can currently be done after the fact, but it would be nice if it could be integrated.

We should provide two api's, Demangle() and DemangleToType()
The DemangleToType() api will return a BNType object containing a type tree for the given type, Demangle() will simply return a string.

[lucasduffey]

Example workaround:

import subprocess
for func in bv.functions:
    if func.name.startswith("__T") or func.name.startswith("_T"):
        func.name = subprocess.check_output(["/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-demangle", "-compact", func.name])

[ccarpenter04]

I'd happily invest 40-80 hours initially (perhaps more even) to improve the demangling support for a variety of different mangling schemes to ensure they get updated and are properly maintained. As with all things of this nature, it would be a cat in mouse game but it would be putting it on plugin developers to maintain instead of the V35 core development team. I have a lot of cases where MSVC or GNU3 symbols aren't demangling correctly when newer compilation toolchains are used, newer compilation settings, etc. We've lost code on one occasion if I recall correctly and the only reason we were able to recover the logic in a reasonable amount of time was due to Sidekick and the fact that we had mangled symbol information (well, DWARF information) and we were able demangle the most important symbols. Had we not had access to demangled symbols we would have had to push back a products release date quite a bit...

[CouleeApps]

As of 4.2.6222 this is now available via the Demangler api. Note that this is a strict plugin layer feature for now, and issues such as #4551 #5920 etc are not resolved