From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/30047] libdw unable to handle DW_TAG_unspecified_type
Date: Thu, 26 Jan 2023 16:39:01 +0000 [thread overview]
Message-ID: <bug-30047-10460-0KTRCnkA1x@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30047-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30047
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
This is slightly tricky, because I think we technically do the right thing
here.
dwfl_module_return_value_location returns that cannot handle DWARF type
description error, which is technically correct, since it is an
unspecified_type.
dwfl_module_return_value_location can return an error (< 0) which means either
bad DWARF or unknown/unhandled type, it can return zero, which means the
function has no return value, or it return the number of DWARF expression
operations (> 0) that describe how to get the value returned by the function.
Sadly we don't have an easy way to distinguish between bad DWARF/type and
cannot handle type.
I think we can change the testcase though, to check for the special case of
DW_TAG_unspecified_type.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-26 16:39 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 [this message]
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
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:
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-30047-10460-0KTRCnkA1x@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).