Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix crash in DWARF indexer
Date: Tue, 07 Jan 2025 07:45:06 -0700	[thread overview]
Message-ID: <87v7uq4r9p.fsf@tromey.com> (raw)
In-Reply-To: <20250106204028.3587605-1-tromey@adacore.com> (Tom Tromey's message of "Mon, 6 Jan 2025 13:40:28 -0700")

>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:

Tom> Iain pointed out a crash in the DWARF indexer when run on a certain D
Tom> program.  The DWARF in this case has a nameless enum class; this
Tom> causes an assertion failure.

Tom> This patch arranges to simply ignore such types.  The fact that an
Tom> enum class is nameless in this case appears to be a compiler bug.

Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32518

I'm also going to merge this one to gdb 16.
It may be a regression; and in any case the fix is very simple.

Tom

      parent reply	other threads:[~2025-01-07 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 20:40 Tom Tromey
2025-01-07 12:10 ` Tom de Vries
2025-01-07 14:40   ` Tom Tromey
2025-01-07 14:45 ` Tom Tromey [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=87v7uq4r9p.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@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