I also just hit this and apparently this is an intentional behavior of xcrun.
Note that this only affects systems that have the so-called command line tools
installed (this is what you get when you install the command line tools without
installing Xcode).
When the command line tools are install
Hi Tamas, First, why DW_AT_MIPS_linkage_name, but not just DW_AT_linkage_name? The later is standartized and currently generated by clang at least on x64. Second, this doesn't help to solve the issue, because this will require parsing all the DWARF types during startup to build a map that breaks DW
The linkage-name attribute was really intended for definitions of objects that
have static memory addresses (static/global variables, and functions), but
adding it to a class description would have an obvious meaning and seems
completely in line with how DWARF works.
Given the size of mangled na
Hi Anton and Jim,
What do you think about storing the mangled type name or the mangled vtable
symbol name somewhere in DWARF in the DW_AT_MIPS_linkage_name attribute? We
are already doing it for the mangled names of functions so extending it to
types shouldn't be too controversial.
Tamas
On Mon,
Thank you for clarification, Jim, you are right, I misunderstood a little bit
what lldb actually does.
It is not that the compiler can't be fixed, it's about the fact that relying on
correspondence of mangled and demangled forms are not reliable enough, so we
are looking for more robust alterna
