[Bug exp/30271] Addresses of static thread_local fields are badly calculated sometimes

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30271

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
Kind of weird DWARF here.  The only location for this
is given by:

 <1><82>: Abbrev Number: 2 (DW_TAG_variable)
    <83>   DW_AT_specification: <0x9f>
    <87>   DW_AT_location    : 10 byte block: e 0 0 0 0 0 0 0 0 e0     
(DW_OP_const8u: 0 0; DW_OP_GNU_push_tls_address or DW_OP_HP_unknown)
    <92>   DW_AT_linkage_name: (indirect string, offset: 0x156):
_ZN9container8tlsvar_0E

It has a forward reference to its defining scope...

gdb currently deals with *backward* references like this by tracking
the DWARF scopes for DIE ranges.  This is needed because gdb's fast
scanner is "forward only", and DWARF provides no way to move up the DIE
tree.

Maybe we can also defer the processing of forward-referencing specifications.

Gosh I hate DWARF.  This stuff is all so needless -- it makes reader
implementation very difficult and provides zero benefit whatsoever.

-- 
You are receiving this mail because:
You are on the CC list for the bug.