Re: [lldb-dev] Resolving dynamic type based on RTTI fails in case of type names inequality in DWARF and mangled symbols

19.12.2017 23:12, Greg Clayton wrote: On Dec 19, 2017, at 12:33 PM, Anton Gorenkov > wrote: Tamas, Greg, thank you, I got the idea how it should work without accelerator tables, but I still cannot figure out how to use/update the existing accelerator

Re: [lldb-dev] Resolving dynamic type based on RTTI fails in case of type names inequality in DWARF and mangled symbols

> On Dec 19, 2017, at 12:33 PM, Anton Gorenkov wrote: > > Tamas, Greg, thank you, I got the idea how it should work without accelerator > tables, but I still cannot figure out how to use/update the existing > accelerator tables. So let me walk trough it once again: > 1. It

Re: [lldb-dev] Resolving dynamic type based on RTTI fails in case of type names inequality in DWARF and mangled symbols

Tamas, Greg, thank you, I got the idea how it should work without accelerator tables, but I still cannot figure out how to use/update the existing accelerator tables. So let me walk trough it once again:   1. It is necessary to perform lookup by mangled name (as all we initially have is mangled

Re: [lldb-dev] lldb test suite on macOS 10.13 (High Sierra)

On 19 December 2017 at 18:06, Greg Clayton wrote: > > The crash hook is needed since ReportCrash on MacOS knows how to dig up a > crash log line for each shared library that is currently loaded in a process > when it generates a crash report. There are settings that we can

Re: [lldb-dev] lldb test suite on macOS 10.13 (High Sierra)

> On Dec 19, 2017, at 4:24 AM, Pavel Labath via lldb-dev > wrote: > > On 18 December 2017 at 23:51, Adrian Prantl wrote: >> I also just hit this and apparently this is an intentional behavior of xcrun. >> >> Note that this only affects systems that

Re: [lldb-dev] lldb test suite on macOS 10.13 (High Sierra)

Jason probably knows about the crash hook. On Tue, Dec 19, 2017 at 4:24 AM, Pavel Labath wrote: > On 18 December 2017 at 23:51, Adrian Prantl wrote: >> I also just hit this and apparently this is an intentional behavior of xcrun. >> >> Note that this only

Re: [lldb-dev] Resolving dynamic type based on RTTI fails in case of type names inequality in DWARF and mangled symbols

I agree with Tamas. The right way to do this it to add the DW_AT_linkage_name to the class. Apple accelerator tables have many different forms, but one is a mapping of type name to exact DIE offset (in the __DWARF_ segment in the __apple_types section). If the mangled name was added to the

Re: [lldb-dev] Resolving dynamic type based on RTTI fails in case of type names inequality in DWARF and mangled symbols

Hi, I thought most compiler still emits DW_AT_MIPS_linkage_name instead of the standard DW_AT_linkage_name but I agree that if we can we should use the standard one. Regarding performance we have 2 different scenarios. On Apple platforms we have the apple accelerator tables to improve load time

Re: [lldb-dev] lldb test suite on macOS 10.13 (High Sierra)

On 18 December 2017 at 23:51, Adrian Prantl wrote: > 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