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 symtab/27453] [meta] DWARF 5 support Date: Thu, 25 Feb 2021 14:43:06 +0000 [thread overview] Message-ID: <bug-27453-4717-sDyWKIUBHV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27453-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27453 Bug 27453 depends on bug 27354, which changed state. Bug 27354 Summary: Dwarf Error: wrong unit_type in compilation unit header (is DW_UT_split_compile (0x05), should be DW_UT_type (0x02) https://sourceware.org/bugzilla/show_bug.cgi?id=27354 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-25 14:43 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-22 2:36 [Bug symtab/27453] New: " tromey at sourceware dot org 2021-02-22 2:36 ` [Bug symtab/27453] " tromey at sourceware dot org 2021-02-22 2:36 ` tromey at sourceware dot org 2021-02-22 2:36 ` tromey at sourceware dot org 2021-02-22 2:36 ` tromey at sourceware dot org 2021-02-22 2:37 ` tromey at sourceware dot org 2021-02-24 22:59 ` vries at gcc dot gnu.org 2021-02-25 14:43 ` vries at gcc dot gnu.org [this message] 2022-04-22 18:33 ` tromey at sourceware dot org 2023-01-04 1:44 ` tromey at sourceware dot org 2023-01-04 1:44 ` tromey at sourceware dot org 2023-01-14 19:40 ` tromey at sourceware dot org 2024-01-18 20:38 ` tromey at sourceware dot org 2024-02-09 18:58 ` tromey at sourceware dot org 2024-03-01 0:15 ` tromey at sourceware 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-27453-4717-sDyWKIUBHV@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: linkBe 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).