Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

om: sgraen...@apple.com [mailto:sgraen...@apple.com] Sent: Tuesday, September 18, 2018 1:35 PM To: Robinson, Paul Cc: LLDB Dev Subject: Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects Hi Paul, thanks for the clarification. Yes, that was my fault. The LTO object DWARF ha

Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

September 14, 2018 11:57 AM > To: LLDB Dev > Subject: Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO > objects > > I made some progress on this and next to many small issues, I found that > DWARFDebugAranges::FindAddress() returns 0 as the CU offset for my fi

Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

er is doing something wrong. --paulr From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Stefan Gränitz via lldb-dev Sent: Friday, September 14, 2018 11:57 AM To: LLDB Dev Subject: Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects I made some progress on thi

Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

I made some progress on this and next to many small issues, I found that DWARFDebugAranges::FindAddress() returns 0 as the CU offset for my file addresses and wonder if this is expected? DWARFDebugAranges::FindAddress() is supposed to read from .debug_aranges section or DW_AT_ranges attributes

Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

Thanks for your replies! >> Right now we assume that each .o file has only on CU so we don't need to >> open all .o files in SymbolFileDWARFDebugMap::CalculateAbilities() which is >> something that gets run when we are trying to figure out which SymbolFile >> plug-in to load. [...] The problem

Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

> On Sep 11, 2018, at 8:48 AM, Greg Clayton wrote: > >> >> On Sep 11, 2018, at 2:55 AM, Stefan Gränitz > > wrote: >> >> Hello everyone >> >> I am investigating a bug that prevents correct breakpoint resolution in LTO >> objects with embedded DWARF (no separate dS

Re: [lldb-dev] Extract compile unit infos from OSO entries for LTO objects

> On Sep 11, 2018, at 2:55 AM, Stefan Gränitz wrote: > > Hello everyone > > I am investigating a bug that prevents correct breakpoint resolution in LTO > objects with embedded DWARF (no separate dSYM file) and tracked it down to > the initialization of SymbolFileDWARFDebugMap. This code seems