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: Thu, 26 Jan 2023 16:39:01 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

dwfl_module_return_value_location returns that cannot handle DWARF type
description error, which is technically correct, since it is an

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

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

  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:

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