Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

Jonas, What are you using to inspect the this pointer? You can use "frame variable" (the equivalent of gdb's "info locals") which just relies on debug info or the expression evaluator e.g. "print". Do both methods show the same problem? Also note that lldb by default will try to discern the

Re: [lldb-dev] Issue: print std unique pointer

I think this is the interesting part: std::__uniq_ptr_impl There is no such type in the example I posted. It looks like the implementation of std::unique_ptr changed, and they added an extra member object. This tells me the fix should be in the data formatter for

Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

> On Feb 28, 2018, at 7:14 PM, Jim Ingham wrote: > > Jonas, > > What are you using to inspect the this pointer? Normally, the Xcode debugger UI. > You can use "frame variable" (the equivalent of gdb's "info locals") which > just relies on debug info or the expression

Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

> On Feb 28, 2018, at 9:27 PM, Jim Ingham wrote: > > Interesting. > > First off, you can turn off fetching dynamic values globally (including in > the Xcode Locals view) by putting: > > settings set target.prefer-dynamic-value no-dynamic-values > in your ~/.lldbinit

Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

Interesting. First off, you can turn off fetching dynamic values globally (including in the Xcode Locals view) by putting: settings set target.prefer-dynamic-value no-dynamic-values in your ~/.lldbinit file. You can toggle this on and off in a session, though Xcode won't notice you've

[lldb-dev] [Bug 36556] New: Module::FindTypes ignores the exact flag in some circumstances

https://bugs.llvm.org/show_bug.cgi?id=36556 Bug ID: 36556 Summary: Module::FindTypes ignores the exact flag in some circumstances Product: lldb Version: unspecified Hardware: PC OS: All Status:

Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

> On Feb 28, 2018, at 1:09 PM, jonas echterhoff wrote: > > > >> On Feb 28, 2018, at 9:27 PM, Jim Ingham wrote: >> >> Interesting. >> >> First off, you can turn off fetching dynamic values globally (including in >> the Xcode Locals view) by putting:

Re: [lldb-dev] Issue: print std unique pointer

All the test cases in TestDataFormatterStdUniquePtr were failing. My std::unique_ptr layout is: (std::unique_ptr) iup = { (std::__uniq_ptr_impl) _M_t = { (std::tuple >) _M_t = { (std::_Tuple_impl<0, int *,

Re: [lldb-dev] [Release-testers] [6.0.0 Release] Release Candidate 3 tagged

Thanks! Added to the web page now. On Tue, Feb 27, 2018 at 9:18 PM, Simon Dardis wrote: > Hi, > > No major issues seen so far for mips. Binaries uploaded. > > SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= >

[lldb-dev] lldb showing wrong type structure for virtual pointer type

Hi, I'm having a problem where lldb will resolve the wrong type for virtual pointers, showing incorrect data for variables. This makes debugging our project very hard. In our project, we commonly have the following structure: class Transform : SomeParentClass { virtual foo(); void

Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

On 02/28/2018 11:31 AM, jonas echterhoff via lldb-dev wrote: I'm using lldb-900.0.64. ^^ ?? Latest official release is 5.0.1; also there are 6.0.0 (at -rc3, the next release) and 7.0.0 (a.k.a SVN trunk). What's the 'version' output of your LLDB

[lldb-dev] [Bug 36547] New: Namespace clash displaying 'this'

https://bugs.llvm.org/show_bug.cgi?id=36547 Bug ID: 36547 Summary: Namespace clash displaying 'this' Product: lldb Version: 6.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P

Re: [lldb-dev] lldb showing wrong type structure for virtual pointer type

> On Feb 28, 2018, at 11:19 AM, Dmitry Antipov wrote: > > On 02/28/2018 11:31 AM, jonas echterhoff via lldb-dev wrote: > >> I'm using lldb-900.0.64. >^^ >?? > Latest official release is 5.0.1; also there are 6.0.0 (at -rc3,