Re: [lldb-dev] Reading eValueTypeLoadAddress with missing compiler type

2017-09-25 Thread Leonardo Bianconi via lldb-dev
e binary that contains debug info and also share which file and function and variable is causing the issue, I might be able to tell you why this is happening. Greg On Sep 18, 2017, at 1:23 PM, Greg Clayton mailto:clayb...@gmail.com>> wrote: A DW_TAG_subprogram's usually has a DW_AT_

Re: [lldb-dev] Reading eValueTypeLoadAddress with missing compiler type

2017-09-19 Thread Leonardo Bianconi via lldb-dev
inary: https://pastebin.com/06UakF24 > > > > > Thanks! > > > > > > > >> -Original Message- > >> From: Greg Clayton [mailto:clayb...@gmail.com] > >> Sent: segunda-feira, 18 de setembro de 2017 17:24 > >> To: Leonardo Bianconi >

Re: [lldb-dev] Reading eValueTypeLoadAddress with missing compiler type

2017-09-19 Thread Leonardo Bianconi via lldb-dev
s is > happening. > > Greg > > > On Sep 18, 2017, at 1:23 PM, Greg Clayton wrote: > > > > A DW_TAG_subprogram's usually has a DW_AT_frame_base DWARF > expression that describes where the frame is. That evaluates to something and > doesn't require any

[lldb-dev] Reading eValueTypeLoadAddress with missing compiler type

2017-09-18 Thread Leonardo Bianconi via lldb-dev
Hi all! I'm facing an issue with a value of lldb_private::Value::eValueTypeLoadAddress type, which cannot be loaded from memory because the compiler type was not filled. That happens obtaining the fame base, which is based on "DW_OP_call_frame_cfa" case (DWARFExpression.cpp:2825). After obtain