*CALL FOR PAPERS / PARTICIPATION*
At FOSDEM 2019, LLVM will again participate with a dedicated devroom,
on February 3rd, in Brussels.
As possibly the largest European Open Source Conference, FOSDEM
attracts more than 600 lectures and over 8000 hackers - many core
contributors of the worlds leading
> On Oct 11, 2018, at 3:55 PM, Davide Italiano wrote:
>
> On Thu, Oct 11, 2018 at 1:38 PM Greg Clayton wrote:
>>
>> I am happy to look at any DWARF expressions you have and help figure out
>> where the change needs to go or how the expression need to be fixed.
>>
>
> Thank you for your hel
> On Oct 11, 2018, at 11:16 AM, Greg Clayton via lldb-dev
> wrote:
>
> DWARF5 finally added the ability to track what each value means on the
> expression stack. Prior to DWARF 5, we had no idea what each entry on the
> expression value stack was (file address, load address
> (Value::eValue
> On Oct 12, 2018, at 9:53 AM, Adrian Prantl via lldb-dev
> wrote:
>
>
>
>> On Oct 11, 2018, at 11:16 AM, Greg Clayton via lldb-dev
>> wrote:
>>
>> DWARF5 finally added the ability to track what each value means on the
>> expression stack. Prior to DWARF 5, we had no idea what each entry
Follow up. This turned out to be a bug in the swift specific support,
so I don't think the DWARF parser code is wrong here.
Thanks!
--
Davide
On Thu, Oct 11, 2018 at 10:52 AM Davide Italiano wrote:
>
> Hi Greg,
> I have this issue that I suspect is a bug in lldb’s handling of DW_OP_deref.
> I wa
> On Oct 12, 2018, at 9:53 AM, Adrian Prantl wrote:
>
>
>
>> On Oct 11, 2018, at 11:16 AM, Greg Clayton via lldb-dev
>> wrote:
>>
>> DWARF5 finally added the ability to track what each value means on the
>> expression stack. Prior to DWARF 5, we had no idea what each entry on the
>> expr
