t;> But:
>>>>
>>>> (lldb) print *this
>>>> (Transform) $5 = {
>>>> [...]
>>>>
>>>> gives me the correct (global) namespace.
>>>>
>>>> Also:
>>>>
>>>> (lldb) frame variab
s -- this
>>>
>>> or equivalently:
>>>
>>> (lldb) frame variable -d no-dynamic-values this
>>>
>>> Is it the dynamic value resolution that's causing the incorrect printing?
>>
&
be even better.
jonas
>
> Jim
>
>
>
>
>> On Feb 28, 2018, at 3:03 AM, jonas echterhoff via lldb-dev
>> wrote:
>>
>>
>>> On Feb 28, 2018, at 11:19 AM, Dmitry Antipov wrote:
>>>
>>> On 02/28/2018 11:31 AM, jonas echterho
> 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
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 bar();
