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, 07 Feb 2023 15:47:52 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
  Attachment #14633|0                           |1
        is obsolete|                            |

--- Comment #6 from Mark Wielaard <mark at klomp dot org> ---
Created attachment 14657
backends: Handle DW_TAG_unspecified_type in dwarf_peeled_die_type

(In reply to Martin Liska from comment #5)
> May I please ping this issue as one needs it with the latest binutils
> release (2.40).

Yes, thanks. I didn't forget, but I changed my mind how to best handle this
See the new patch. This changes the code so that an DW_TAG_unspecified_type is
treated just as if the function doesn't have a return type. I think that is a
better fix because there might be more code out there that uses
dwfl_module_return_value_location and might not handle an error in this case.
And there isn't actually much that can be done with an unspecified type, for
normal cases it is as if there is no return type.

I did adjust the testcase to show how you can see whether it is a missing
return type or an unspecified return type in case you program does care.

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

  parent reply	other threads:[~2023-02-07 15:47 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 [this message]
2023-02-14  8:25 ` mliska at suse dot cz
2023-02-14 15:34 ` mark at klomp dot org
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).