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/29321] [gdb] read.h:311: internal-error: unit_type: Assertion `m_unit_type != 0' failed Date: Wed, 06 Jul 2022 16:13:33 +0000 [thread overview] Message-ID: <bug-29321-4717-Upb8kqHBfM@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29321-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29321 --- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> --- On openSUSE Tumbleweed, with gcc-12 defaulting to dwarf-5, I run into this PR with native: ... FAIL: gdb.dwarf2/count.exp: runto: run to main (GDB internal error) FAIL: gdb.dwarf2/implptrconst.exp: runto: run to main (GDB internal error) FAIL: gdb.dwarf2/implptrpiece.exp: runto: run to main (GDB internal error) ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-06 16:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-06 12:17 [Bug symtab/29321] New: " vries at gcc dot gnu.org 2022-07-06 12:45 ` [Bug symtab/29321] " vries at gcc dot gnu.org 2022-07-06 16:13 ` vries at gcc dot gnu.org [this message] 2022-07-08 13:58 ` vries at gcc dot gnu.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-29321-4717-Upb8kqHBfM@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).