[PATCH] D68133: [Symbolize] Use the local MSVC C++ demangler instead of relying on dbghelp. NFC.

Nico Weber via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue Oct 8 12:50:22 PDT 2019


thakis added a comment.

In D68133#1694180 <https://reviews.llvm.org/D68133#1694180>, @mstorsjo wrote:

> Had to revert this one, as it broke sanitizer tests: http://lab.llvm.org:8011/builders/sanitizer-windows/builds/52441
>
> So apparently it seems (again) like it would be useful if the llvm microsoft demangler could be configured to leave out parts of the output. In D68134 <https://reviews.llvm.org/D68134> (in LLDB) we can consider changing the testcases to include the new demangler output, but there was a concern that there might be cases within LLDB that try to parse the demangled function names. And here it significantly changes the libfuzzer deduplication token output, which I think also isn't ideal.
>
> @thakis - you brought it up earlier that adding options to it could be possible. Do you, who I think is familiar with that demangler, have time to make a PoC of it? Otherwise I might have a stab at it sometimes later...


That links is dead. Which customization is needed here? microsoftDemangle() already gets a Flags argument; we can just add more flags to it.


Repository:
  rL LLVM

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D68133/new/

https://reviews.llvm.org/D68133





More information about the llvm-commits mailing list