I think the type "T" found in the Dwarf info would have to have come from
> the same compile unit that the "normally declared" type "T" came from, i.e.
> your "DW_AT_name(...)" function would have to guarantee that. There's
> nothing stopping the same type name from being used in different ways in
endor to
decide about DW_AT_name?
2018-03-06 11:08 GMT-08:00 Michael Eager :
> On 03/06/2018 10:37 AM, Roman Popov wrote:
>
>> Hi everyone,
>> I'm working on a dynamic analysis tool that needs runtime reflection in
>> C++. Since C++ has no standardized runtime reflec
Hi everyone,
I'm working on a dynamic analysis tool that needs runtime reflection in
C++. Since C++ has no standardized runtime reflection, I'm using DWARF as a
source of reflection metadata.
Is it a legitimate use-case from DWARF standard point of view?
It has been working great for me until I'v
