From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 17884385840F; Wed, 25 Jan 2023 01:21:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 17884385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1674609708; bh=hPR/pMD3Vmd5prQ7pwDTzkEUmJIG0ZcI1zP0ZPz2Jno=; h=From:To:Subject:Date:From; b=yyIYdbKB2AfXvKR7u7Ynn3RgTZ6C0nZ7Qqvzu8f7ASRHl62Ao8t8miDRXX+SNy110 6rWEhRVkdG+cIPO1f27+KPCtdMii86jRQhVRU7wOVWqE/vuQhzd7rwShT2sBC3nrZT uif4YYn+QiLxi2K52SkLFqx5Auvg22f+8cx/Nnbs= From: "raj.khem at gmail dot com" To: elfutils-devel@sourceware.org Subject: [Bug libdw/30047] New: libdw unable to handle DW_TAG_unspecified_type Date: Wed, 25 Jan 2023 01:21:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: libdw X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: raj.khem at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30047 Bug ID: 30047 Summary: libdw unable to handle DW_TAG_unspecified_type Product: elfutils Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: libdw Assignee: unassigned at sourceware dot org Reporter: raj.khem at gmail dot com CC: elfutils-devel at sourceware dot org Target Milestone: --- GNU assembler starting with 2.40 release is generating DW_TAG_unspecified_t= ype for assembly files [1] this is fixed in gdb [2], however, it shows up as on= e of test failures in elfutils=20 % ./funcretval () _start: ./funcretval: dwfl_module_return_value_location: cannot handle D= WARF type description The reason is that glibc startup files e.g. (/usr/lib/Scrt1.o) is built from assembly routines and when compiled with toolchain using binutils 2.40 gets these DW_TAG_unspecified_type entries emitted into its debug segments which inturn get into the testcases when they are built in elfutils testsuites native.c =3D=3D=3D=3D=3D=3D=3D=3D=3D #include int main () { while (1) pause (); return 0;} gcc -g native.c ./funcretval then results in this error and failure in elfutils testcases /usr/lib/elfutils/ptest/tests/funcretval: dwfl_module_return_value_location: cannot handle DWARF type description FAIL: run-native-test.sh I think libdw has to implement handling DW_TAG_unspecified_type, since it w= ill start showing up everywhere soon as 2.40 binutils trickle into downstream distributions and they do mass-rebuilds. [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3D29559 [2] https://sourceware.org/bugzilla/show_bug.cgi?id=3D29558 --=20 You are receiving this mail because: You are on the CC list for the bug.=