https://sourceware.org/bugzilla/show_bug.cgi?id=29559
Nick Clifton <nickc at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at sourceware dot org |nickc at redhat dot com
--- Comment #1 from Nick Clifton <nickc at redhat dot com> ---
Hi Tom,
[For the record the patch that introduced this bug was intended to fix PR
29517].
> <0><100>: Abbrev Number: 3 (DW_TAG_unspecified_type)
> <0><101>: Abbrev Number: 1 (DW_TAG_compile_unit)
OK, so you are saying that the DW_TAG_unspecified_type is in the wrong place ?
Presumably it should be after DW_TAG_subprogram. IE, something like this:
<0><101>: Abbrev Number: 1 (DW_TAG_compile_unit)
<102> DW_AT_stmt_list : 0x123
<106> DW_AT_low_pc : 0x4004ac
<10e> DW_AT_high_pc : 11
<10f> DW_AT_name : test2.s
<113> DW_AT_comp_dir : /home/vries/gdb_versions/devel
<117> DW_AT_producer : GNU AS 2.39.50
<11b> DW_AT_language : 32769 (MIPS assembler)
<1><11d>: Abbrev Number: 2 (DW_TAG_subprogram)
<11e> DW_AT_name : (indirect string, offset: 0x241): foo
<122> DW_AT_external : 1
<122> DW_AT_type : <0x133>
<123> DW_AT_low_pc : 0x4004ac
<12b> DW_AT_high_pc : 11
<1><133>: Abbrev Number: 3 (DW_TAG_unspecified_type)
I will try to fix this. I originally placed the unspecified tag at the start
of the CU information because I found that I could not otherwise compute the
correct offset for it. I will just have to try harder.
Cheers
Nick
--
You are receiving this mail because:
You are on the CC list for the bug.
