public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27588] dwz: libxul.so: loclistptr attribute, yet no .debug_loc section
Date: Tue, 16 Mar 2021 10:08:17 +0000	[thread overview]
Message-ID: <bug-27588-11298-6GEVEpra14@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27588-11298@http.sourceware.org/bugzilla/>

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

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
So, this is related to this CU:
...
  Compilation Unit @ offset 0x37d3:
   Length:        0x8f (32-bit)
   Version:       3
   Abbrev Offset: 0x602
   Pointer Size:  8
 <0><37de>: Abbrev Number: 1 (DW_TAG_compile_unit)
    <37df>   DW_AT_low_pc      : 0x4a89440
    <37e7>   DW_AT_high_pc     : 0x4a8d580
    <37ef>   DW_AT_stmt_list   : 0x12e55
    <37f3>   DW_AT_name        :
/home/abuild/rpmbuild/BUILD/thunderbird-78.8.1/third_party/dav1d/src/x86/cdef.asm
    <3845>   DW_AT_producer    : NASM 2.15.05
    <3852>   DW_AT_language    : 32769  (MIPS assembler)
 <1><3854>: Abbrev Number: 2 (DW_TAG_subprogram)
    <3855>   DW_AT_low_pc      : 0x4a89440
    <385d>   DW_AT_frame_base  : 0x0 (location list)
 <1><3861>: Abbrev Number: 0
 <0><3862>: Abbrev Number: 0
 <-1><3863>: Abbrev Number: 0
...

The dwarf version of the CU is 3, so a .debug_loc section is expected to
contain the location list for DW_AT_frame_base.

However, the binary does not contain a .debug_loc section:
...
$ readelf -S -W libxul.so | grep .debug_
  [31] .debug_aranges    PROGBITS        0000000000000000 7d238a0 02a5d0 00    
 0   0 16
  [32] .debug_pubnames   PROGBITS        0000000000000000 7d4de70 c25c3f 00    
 0   0  1
  [33] .debug_info       PROGBITS        0000000000000000 8973aaf 143b0f2 00   
  0   0  1
  [34] .debug_abbrev     PROGBITS        0000000000000000 9daeba1 001195 00    
 0   0  1
  [35] .debug_line       PROGBITS        0000000000000000 9dafd36 730cdf 00    
 0   0  1
  [36] .debug_str        PROGBITS        0000000000000000 a4e0a15 159d458 01 
MS  0   0  1
  [37] .debug_pubtypes   PROGBITS        0000000000000000 ba7de6d 000c60 00    
 0   0  1
  [38] .debug_ranges     PROGBITS        0000000000000000 ba7eacd 98b200 00    
 0   0  1
  [39] .debug_line_str   PROGBITS        0000000000000000 c409ccd 0001b8 01  MS
 0   0  1
  [40] .debug_loclists   PROGBITS        0000000000000000 c409e85 000060 00    
 0   0  1
  [41] .debug_rnglists   PROGBITS        0000000000000000 c409ee5 000042 00    
 0   0  1
...

So, I'd say the error message is correct.

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

  reply	other threads:[~2021-03-16 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  9:17 [Bug default/27588] New: " mliska at suse dot cz
2021-03-16 10:08 ` vries at gcc dot gnu.org [this message]
2021-03-16 10:36 ` [Bug default/27588] " mliska at suse dot cz
2021-03-16 10:38 ` mliska at suse dot cz
2021-03-16 10:49 ` vries at gcc dot gnu.org
2021-03-16 11:12 ` mliska at suse dot cz
2021-03-16 14:21 ` vries at gcc dot gnu.org
2021-03-16 14:23 ` mliska at suse dot cz
2021-05-17  8:57 ` vries at gcc dot gnu.org
2023-01-16 10:14 ` mliska at suse dot cz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-27588-11298-6GEVEpra14@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=dwz@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).