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 exp/20630] gdb crash from TYPE_OBJFILE_OWNED Date: Sat, 18 Jun 2022 16:43:52 +0000 [thread overview] Message-ID: <bug-20630-4717-ef0TghkDDo@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-20630-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=20630 --- 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=8e2da165187907a570a33eee7e56ce16fc597a40 commit 8e2da165187907a570a33eee7e56ce16fc597a40 Author: Tom Tromey <tom@tromey.com> Date: Sun Jun 5 11:28:10 2022 -0600 Fix assertion failure in copy_type PR exp/20630 points out a simple way to cause an assertion failure in copy_type -- but this was found in the wild a few times as well. copy_type only works for objfile-owned types, but there isn't a deep reason for this. This patch fixes the bug by updating copy_type to work for any sort of type. Better would perhaps be to finally implement type GC, but I still haven't attempted this. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=20630 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-18 16:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-20630-4717@http.sourceware.org/bugzilla/> 2020-04-11 11:21 ` ssbssa at sourceware dot org 2022-06-05 17:24 ` tromey at sourceware dot org 2022-06-05 17:25 ` tromey at sourceware dot org 2022-06-05 17:30 ` tromey at sourceware dot org 2022-06-18 16:43 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-18 16:45 ` tromey at sourceware dot org 2023-03-17 13:55 ` 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-20630-4717-ef0TghkDDo@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).