Greg Clayton via lldb-dev wrote:
> Please do submit this for review, yes.
Just a bump to observe that debug information still behaves as if it's not
there
in binaries built with LTO on Mac (except possibly in very simple executables
that don't link to any shared libraries).
R.
__
> I attached a modified patch with the calls to ExtractDIEsIfNeeded() on
> separate threads.
>
> Should I submit it for review ?
>
> -Philippe
>
> From: Greg Clayton [gclay...@apple.com]
> Sent: Tuesday, May 03, 2016 5:02 PM
> To: Philippe Lavoie
> Cc: lldb-de
From: Greg Clayton [gclay...@apple.com]
Sent: Tuesday, May 03, 2016 5:02 PM
To: Philippe Lavoie
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] LTO debug info
> On May 3, 2016, at 6:35 AM, Philippe Lavoie
> wrote:
>
> The code accessing another CU wh
et(die_offset);
>}
>}
>return DWARFDIE(); // Not found
> }
>
> ________________
> From: lldb-dev [lldb-dev-boun...@lists.llvm.org] on behalf of Philippe Lavoie
> via lldb-dev [lldb-dev@lists.llvm.org]
> Sent: Friday, April 29,
@lists.llvm.org] on behalf of Philippe Lavoie
via lldb-dev [lldb-dev@lists.llvm.org]
Sent: Friday, April 29, 2016 3:27 PM
To: Greg Clayton
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] LTO debug info
> So the main question is why is anything that is indexing the current CU only,
> ac
On Monday April 25 2016 20:37:00 Philippe Lavoie via lldb-dev wrote:
>Hello,
>
>We noticed an issue with dwarf parsing when debugging a large application
>compiled with LTO.
I don't know if this is related or not, but on OS X it seems that using LTO
causes debug info to be lost altogether (thoug
t;1773> DW_AT_name : (indirect string, offset: 0xd9): x
<1777> DW_AT_decl_file : 1
<1778> DW_AT_decl_line : 3
<1779> DW_AT_type: <0x1741>
From: Greg Clayton [gclay.
ccess a stale or
> invalid DWARFCompileUnit::m_die_array ...
So the main question is why is anything that is indexing the current CU only,
accessing anything from another CU? It can't and shouldn't. That is the bug.
> -Philippe
>
> ________
&
PM
To: Philippe Lavoie
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] LTO debug info
> On Apr 25, 2016, at 1:37 PM, Philippe Lavoie via lldb-dev
> wrote:
>
> Hello,
>
> We noticed an issue with dwarf parsing when debugging a large application
> compiled with LTO.
>
>
> On Apr 25, 2016, at 1:37 PM, Philippe Lavoie via lldb-dev
> wrote:
>
> Hello,
>
> We noticed an issue with dwarf parsing when debugging a large application
> compiled with LTO.
>
> Since an LTO application's debug info can have inter-compile-unit references,
> (for example: a type defined
10 matches
Mail list logo
