public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29128] "internal-error: find_pc_sect_compunit_symtab: Assertion `result != nullptr' failed" while debugging asm program
Date: Thu, 26 May 2022 17:50:59 +0000	[thread overview]
Message-ID: <bug-29128-4717-TS8VQuW6Z5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29128-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29128

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=834eaf9201c18efc5b888f3cd116dd7856bec759

commit 834eaf9201c18efc5b888f3cd116dd7856bec759
Author: Tom Tromey <tom@tromey.com>
Date:   Thu May 12 16:37:52 2022 -0600

    Fix crash in new DWARF indexer

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

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

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29128

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 11:49 [Bug gdb/29128] New: " simark at simark dot ca
2022-05-07 12:07 ` [Bug gdb/29128] " simark at simark dot ca
2022-05-07 15:06 ` tromey at sourceware dot org
2022-05-07 15:25 ` tromey at sourceware dot org
2022-05-07 20:45 ` simark at simark dot ca
2022-05-21 14:57 ` tromey at sourceware dot org
2022-05-26 17:50 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-26 17:51 ` 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-29128-4717-TS8VQuW6Z5@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).