public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/29558] [gdb/symtab] Handle gas-generated debug info (DW_TAG_unspecified_type)
Date: Thu, 26 Jan 2023 17:29:16 +0000 [thread overview]
Message-ID: <bug-29558-4717-PETicoUg2v@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29558-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29558
--- Comment #10 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #9)
> Created attachment 14632 [details]
> tests: Handle DW_TAG_unspecified_type in funcretval test
>
> This patch just fixes the testcase to check for DW_TAG_unspecified_type as
> return type.
> With your test binary tests/funcretval now prints:
>
> () _start: returns unspecified type
> () main: return value location: {0x50, 0}
>
> But maybe a better fix is for dwfl_module_return_value_location to return
> zero (which technically means that the function doesn't have a return value).
>
> Opinions?
Sorry, this patch was for elfutils, specifically
https://sourceware.org/bugzilla/show_bug.cgi?id=30047 I was just looking how
gdb handled this.
Apologies.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-01-26 17:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 8:38 [Bug gdb/29558] New: " vries at gcc dot gnu.org
2022-09-08 8:38 ` [Bug gdb/29558] " vries at gcc dot gnu.org
2022-09-08 8:46 ` vries at gcc dot gnu.org
2022-09-08 8:51 ` vries at gcc dot gnu.org
2022-09-08 9:01 ` vries at gcc dot gnu.org
2022-09-08 10:45 ` vries at gcc dot gnu.org
2022-09-08 10:45 ` vries at gcc dot gnu.org
2022-09-08 12:20 ` vries at gcc dot gnu.org
2022-09-08 13:06 ` [Bug symtab/29558] " vries at gcc dot gnu.org
2022-09-11 7:02 ` vries at gcc dot gnu.org
2023-01-26 17:28 ` mark at klomp dot org
2023-01-26 17:29 ` mark at klomp dot org [this message]
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-29558-4717-PETicoUg2v@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).