Roman,
Thanks for verifying. I am trying to see how far this goes.
It would be interesting to look at the GCC DWARF for this. If you can attach a
copy of the binary, I would like to take a look to see if the DWARF itself has
any offending type info where it sometimes has the 'u' and other times
Yes, you're right. When I replaced unsigned with signed int it works
properly.
2017-02-10 19:46 GMT+03:00 Greg Clayton :
>
> On Feb 10, 2017, at 12:55 AM, Roman Popov wrote:
>
> Thanks Greg,
>
> So here is another case when LLDB fails to resolve dynamic type. Compiled
> with G++5.4 on Ubuntu 16
> On Feb 10, 2017, at 12:55 AM, Roman Popov wrote:
>
> Thanks Greg,
>
> So here is another case when LLDB fails to resolve dynamic type. Compiled
> with G++5.4 on Ubuntu 16.04.
>
> Here I want to get dynamic type for some variable apb_memories
>
> (lldb) expr -d no-run -- apb_memories
> (sc
Thanks Greg,
So here is another case when LLDB fails to resolve dynamic type. Compiled
with G++5.4 on Ubuntu 16.04.
Here I want to get dynamic type for some variable apb_memories
(lldb) expr -d no-run -- apb_memories
(sc_core::sc_object *) $3 = 0x00cb6aa8
(lldb) memory read --format a
> On Feb 6, 2017, at 5:58 PM, Roman Popov wrote:
>
> Hello,
> I just found out that sometimes I don't get correct dynamic type in LLDB even
> if I compile with g++. How can I get typeinfo/vtable dump from LLDB to check
> if it is still the same name matching issue?
Stop where dynamic typi
; *To:* Robinson, Paul
> *Cc:* Zachary Turner; LLDB Dev (lldb-dev@lists.llvm.org)
> *Subject:* Re: [lldb-dev] RTTI does not work stable in LLDB.
>
>
>
>
>
> On Feb 6, 2017, at 3:38 PM, Robinson, Paul wrote:
>
>
>
> It's not practical for the DWARF to try to identify the
does not work stable in LLDB.
On Feb 6, 2017, at 3:38 PM, Robinson, Paul
mailto:paul.robin...@sony.com>> wrote:
It's not practical for the DWARF to try to identify the actual address of the
vtable; that address might not be available.
it seems like we could hang onto the linkage_
> On Feb 6, 2017, at 3:38 PM, Robinson, Paul wrote:
>
> It's not practical for the DWARF to try to identify the actual address of the
> vtable; that address might not be available.
> it seems like we could hang onto the linkage_name of the vtable though,
> somewhere, so you wouldn't be relying
elpful to have these things come up *before* the next rev of
the spec is frozen. Just sayin'. ☺
From: Greg Clayton [mailto:gclay...@apple.com]
Sent: Monday, February 06, 2017 2:35 PM
To: Zachary Turner
Cc: Robinson, Paul; LLDB Dev (lldb-dev@lists.llvm.org)
Subject: Re: [lldb-dev] RTTI does not
r it matches any given demangler's opinion of the name.
>> --paulr
>> <>
>> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org
>> <mailto:lldb-dev-boun...@lists.llvm.org>] On Behalf Of Greg Clayton via
>> lldb-dev
>> Sent: Monday, February 06,
[mailto:lldb-dev-boun...@lists.llvm.org
> ] *On Behalf Of *Greg Clayton via
> lldb-dev
> *Sent:* Monday, February 06, 2017 11:08 AM
> *To:* Greg Clayton
> *Cc:* lldb-dev@lists.llvm.org
> *Subject:* Re: [lldb-dev] RTTI does not work stable in LLDB.
>
> So I found th
Behalf Of Greg
> Clayton via lldb-dev
> Sent: Monday, February 06, 2017 11:08 AM
> To: Greg Clayton
> Cc: lldb-dev@lists.llvm.org
> Subject: Re: [lldb-dev] RTTI does not work stable in LLDB.
>
> So I found the problem. This is a compiler bug. The DWARF for this type l
.org] *On Behalf Of *Greg
> Clayton via lldb-dev
> *Sent:* Monday, February 06, 2017 11:08 AM
> *To:* Greg Clayton
> *Cc:* lldb-dev@lists.llvm.org
> *Subject:* Re: [lldb-dev] RTTI does not work stable in LLDB.
>
>
>
> So I found the problem. This is a
f the name.
--paulr
From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Greg
Clayton via lldb-dev
Sent: Monday, February 06, 2017 11:08 AM
To: Greg Clayton
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] RTTI does not work stable in LLDB.
So I found the problem. This is a com
So I found the problem. This is a compiler bug. The DWARF for this type looks
like:
0x65da: TAG_structure_type [112] *
AT_containing_type( {0x6628} )
AT_name( "derived0" )
AT_byte_size( 0x08 )
AT_decl_file( "/
I am looking at this now. I will let you know what I find.
Greg
> On Feb 6, 2017, at 10:00 AM, Roman Popov wrote:
>
> Yes, that was my thought.
>
> FYI, checked in GDB: it's working correctly on this testcase showing correct
> dynamic type in both cases.
>
> 2017-02-06 9:48 GMT-08:00 Greg C
Yes, that was my thought.
FYI, checked in GDB: it's working correctly on this testcase showing
correct dynamic type in both cases.
2017-02-06 9:48 GMT-08:00 Greg Clayton :
> You have found a bug. It should be reporting this correctly but it isn’t.
> I verified it fails on MacOSX.
>
> Greg Clayto
You have found a bug. It should be reporting this correctly but it isn’t. I
verified it fails on MacOSX.
Greg Clayton
> On Feb 5, 2017, at 1:19 PM, Roman Popov via lldb-dev
> wrote:
>
> Hello,
> I'm observing very strange LLDB behavior: it does not always shows a correct
> dynamic type when
Hello,
I'm observing very strange LLDB behavior: it does not always shows a
correct dynamic type when I ask for.
Originally I was working with LLDB 3.9, but it looks like trunk version
behaves the same strange way.
I was able to capture this behavior in a small code snippet:
#include
#include
19 matches
Mail list logo
