public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29558] [gdb/symtab] Handle gas-generated debug info (DW_TAG_unspecified_type)
Date: Thu, 08 Sep 2022 08:51:07 +0000 [thread overview]
Message-ID: <bug-29558-4717-hlDvMvnz47@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 #3 from Tom de Vries <vries at gcc dot gnu.org> ---
In the dwarf-5 standard I read:
...
For each compilation unit compiled with a DWARF producer, a contribution is
made to the .debug_info section of the object file. Each such contribution
consists of a compilation unit header followed by a single DW_TAG_compile_unit
or DW_TAG_partial_unit debugging information entry, together with its children.
...
Ok, so this is in fact incorrect dwarf.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-08 8:51 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 [this message]
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
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-hlDvMvnz47@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).