Re: [lldb-dev] [llvm-dev] [cfe-dev] What version comes after 3.9? (Was: [3.9 Release] Release plan and call for testers)

2016-06-18 Thread Chris Lattner via lldb-dev
> On Jun 18, 2016, at 9:16 PM, Chris Lattner via llvm-dev > wrote: > > On Jun 14, 2016, at 1:32 AM, Richard Smith via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: >> I think that this is the right approach, and we happen to have a natural >> forcing function here: opaque pointer types. I

Re: [lldb-dev] [cfe-dev] What version comes after 3.9? (Was: [3.9 Release] Release plan and call for testers)

2016-06-18 Thread Chris Lattner via lldb-dev
On Jun 14, 2016, at 1:32 AM, Richard Smith via cfe-dev wrote: > I think that this is the right approach, and we happen to have a natural > forcing function here: opaque pointer types. I think we should increment the > major version number when opaque pointer types are here, as it will be a > m

[lldb-dev] GetSymbolContext(lldb.eSymbolContextEverything)

2016-06-18 Thread Kamenee Arumugam via lldb-dev
Hi, I am trying program using Lldb Python API to get an output exactly same when I run this command "image lookup --address 0x000405a6 --verbose". But when I print return value of GetSymbolContext(lldb.eSymbolContextEverything), it doesnt contain the decoding of local variables which the above