public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix crash in new DWARF indexer
Date: Thu, 26 May 2022 11:36:19 -0600	[thread overview]
Message-ID: <87mtf46vsc.fsf@tromey.com> (raw)
In-Reply-To: <20220513000032.3056175-1-tom@tromey.com> (Tom Tromey's message of "Thu, 12 May 2022 18:00:32 -0600")

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

Tom> PR gdb/29128 points out a crash in the new DWARF index code.  This
Tom> happens if the aranges for a CU claims a PC, but the symtab that is
Tom> created during CU expansion does not actually contain the PC.  This
Tom> can only occur due to bad debuginfo, but at the same time, gdb should
Tom> not crash.

Tom> This patch fixes the bug and further merges some code into
Tom> dwarf2_base_index_functions.  This merger helps prevent the same issue
Tom> from arising from the other index implementations.

I'm going to check this in now.

Tom

      reply	other threads:[~2022-05-26 17:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  0:00 Tom Tromey
2022-05-26 17:36 ` 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=87mtf46vsc.fsf@tromey.com \
    --to=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).