[gdb/testsuite] Fix .debug_aranges in gdb.dlang/watch-loc.c
authorTom de Vries <tdevries@suse.de>
Wed, 22 Apr 2020 11:17:32 +0000 (13:17 +0200)
committerTom de Vries <tdevries@suse.de>
Wed, 22 Apr 2020 11:17:32 +0000 (13:17 +0200)
commit714534e1b88608f92b6946d8e5a24ea51a40e363
tree650a77984bcfe667a4ffc2a4d1ec957a5d62e9fc
parent16a7dbf4c187753209072caa5b41757a7baa1c8d
[gdb/testsuite] Fix .debug_aranges in gdb.dlang/watch-loc.c

While investigating PR25862 (an assertion failure with target board
cc-with-debug-names), I noticed that the .debug_aranges section in
gdb.dlang/watch-loc.c contains a hardcoded 0x1000:
...
"      .4byte  _Dmain \n"      // Address
"      .4byte  0x1000 \n"      // Length
...

Fix this by using the actual length of _Dmain, along the lines of how that
is done in gdb.mi/dw2-ref-missing-frame-func.c:
...
"      .4byte  _Dmain_end - _Dmain \n" // Length
...
such that the .debug_aranges entry:
...
    Address    Length
    004004a7 0000000b
    00000000 00000000
...
matches the addresses found in the corresponding CU:
...
 <2><fd>: Abbrev Number: 6 (DW_TAG_subprogram)
    <fe>   DW_AT_name        : _Dmain
    <105>   DW_AT_low_pc      : 0x4004a7
    <10d>   DW_AT_high_pc     : 0x4004b2
...

With this fix the assertion failure is no longer triggered for
gdb.dlang/watch-loc.exp.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2020-04-22  Tom de Vries  <tdevries@suse.de>

* gdb.dlang/watch-loc.c (.debug_aranges): Fix _Dmain length.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.dlang/watch-loc.c