public inbox for
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <>
Subject: [Bug libdw/30047] libdw unable to handle DW_TAG_unspecified_type
Date: Tue, 14 Feb 2023 15:34:23 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #8 from Mark Wielaard <mark at klomp dot org> ---
commit f2c522567ad63ac293535fba9704895e685ab5bc
Author: Mark Wielaard <>
Date:   Thu Jan 26 18:19:15 2023 +0100

    backends: Handle DW_TAG_unspecified_type in dwarf_peeled_die_type

    binutils 2.40 introduces DW_TAG_unspecified_type for assembly
    functions with an unknown return type. This breaks the testcase because dwfl_module_return_value_location
    returns an error for such functions because it cannot determine the
    return value location. Fix that by treating DW_TAG_unspecified_type
    as if the DIE doesn't have a DW_AT_type.

    Also update the testcase to explicitly checking for
    DW_TAG_unspecified_type and printing "returns unspecified type".

    Signed-off-by: Mark Wielaard <>

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

  parent reply	other threads:[~2023-02-14 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25  1:21 [Bug libdw/30047] New: " raj.khem at gmail dot com
2023-01-25  1:30 ` [Bug libdw/30047] " raj.khem at gmail dot com
2023-01-26 16:39 ` mark at klomp dot org
2023-01-26 17:30 ` mark at klomp dot org
2023-01-26 17:41 ` raj.khem at gmail dot com
2023-02-06 13:11 ` mliska at suse dot cz
2023-02-07 15:47 ` mark at klomp dot org
2023-02-14  8:25 ` mliska at suse dot cz
2023-02-14 15:34 ` mark at klomp dot org [this message]
2023-03-02 13:27 ` 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:

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

  git send-email \ \ \ \

* 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).