--
dodji at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassigned at gcc dot gnu |dodji at gcc dot gnu dot org
|dot org
--- Comment #10 from dodji at gcc dot gnu dot org 2010-03-18 12:53 ---
Bug no more present in 4.5
--
dodji at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #9 from dodji at gcc dot gnu dot org 2010-03-17 21:15 ---
The situation has change quite a lot since gcc 4.3.0.
Now a DW_TAG_member is emitted for the static member variable, and only one
DW_TAG_variable is emitted to represent the variable definition.
So I guess the bug
--- Comment #8 from swagiaal at redhat dot com 2008-12-01 16:12 ---
DW_AT_MIPS_linkage_name should be removed from GCC only after the DW_AT_name
scoping/qualification will get fully fixed. GDB currently already contains
the
DW_AT_MIPS_linkage_name reader and there is probably no
--- Comment #6 from swagiaal at redhat dot com 2008-11-28 16:33 ---
(2) Defining declaration 86 should point by DW_AT_specification to its
non-defining declaration 37. (The DWARF citation is here from Dodji.)
(But I do not see these two problems as real issues for debugging.)
--- Comment #7 from jan dot kratochvil at redhat dot com 2008-11-29 00:23
---
(In reply to comment #6)
I ran into this issue because gdb was only reading die 0x86 for variable
'elsewhere' (I have not looked into why). The problem is that without proper
scoping on an abstract_origin
--- Comment #5 from jan dot kratochvil at redhat dot com 2008-11-28 01:36
---
(In reply to comment #4)
First, I think the DIE representing the defining declaration of A::elsewhere
in class2.c should have a DW_AT_specification pointing back to the DIE
representing the declaration or
--- Comment #4 from dodji at gcc dot gnu dot org 2008-11-01 11:03 ---
I could reproduce this on 4.3 and trunk (4.4).
Actually I think there are several problems here.
First, I think the DIE representing the defining declaration of A::elsewhere in
class2.c should have a
