public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27743] Internal error psymtab.c Date: Mon, 26 Apr 2021 15:55:45 +0000 [thread overview] Message-ID: <bug-27743-4717-9SQh474DvC@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27743-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27743 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Target Milestone|10.2 |11.1 Status|UNCONFIRMED |RESOLVED --- Comment #26 from Tom Tromey <tromey at sourceware dot org> --- I've checked in the fix. It isn't in the 10.2 release, but I did put the fix on the gdb 10 branch. There probably won't be a 10.3, but it's there in case someone wants to do their own build from git, or pick the patch into their local repo. git trunk doesn't have the bug, but I've put the test case there. I've reset the target milestone to reflect that this isn't really in 10.2. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-26 15:55 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 12:57 [Bug gdb/27743] New: " ilia.motornyi at jetbrains dot com 2021-04-16 13:12 ` [Bug gdb/27743] " ilia.motornyi at jetbrains dot com 2021-04-16 14:09 ` simark at simark dot ca 2021-04-16 14:31 ` ilia.motornyi at jetbrains dot com 2021-04-17 3:04 ` cn.yiki at gmail dot com 2021-04-17 13:06 ` simark at simark dot ca 2021-04-17 15:46 ` tromey at sourceware dot org 2021-04-18 4:56 ` cn.yiki at gmail dot com 2021-04-19 0:56 ` simark at simark dot ca 2021-04-19 0:56 ` simark at simark dot ca 2021-04-19 1:51 ` tromey at sourceware dot org 2021-04-19 1:54 ` simark at simark dot ca 2021-04-19 11:55 ` cn.yiki at gmail dot com 2021-04-19 14:04 ` ilia.motornyi at jetbrains dot com 2021-04-19 14:23 ` cn.yiki at gmail dot com 2021-04-19 14:41 ` ilia.motornyi at jetbrains dot com 2021-04-19 14:45 ` simark at simark dot ca 2021-04-19 14:46 ` simark at simark dot ca 2021-04-23 12:03 ` ilia.motornyi at jetbrains dot com 2021-04-23 12:54 ` ilia.motornyi at jetbrains dot com 2021-04-23 15:27 ` tromey at sourceware dot org 2021-04-23 15:34 ` tromey at sourceware dot org 2021-04-23 18:14 ` tromey at sourceware dot org 2021-04-23 18:23 ` tromey at sourceware dot org 2021-04-23 18:49 ` brobecker at gnat dot com 2021-04-26 15:39 ` cvs-commit at gcc dot gnu.org 2021-04-26 15:40 ` cvs-commit at gcc dot gnu.org 2021-04-26 15:53 ` cvs-commit at gcc dot gnu.org 2021-04-26 15:55 ` tromey at sourceware dot org [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=bug-27743-4717-9SQh474DvC@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).