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 symtab/30846] [gdb/symtab] incorrect parent for forward spec (inter-cu case) Date: Tue, 16 Apr 2024 17:55:29 +0000 [thread overview] Message-ID: <bug-30846-4717-1prEJ4LOtI@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30846-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30846 --- Comment #4 from Sourceware Commits <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=ec9a843791b2d542575c27d7f5f154388765761e commit ec9a843791b2d542575c27d7f5f154388765761e Author: Tom de Vries <tdevries@suse.de> Date: Sun Sep 24 12:33:59 2023 +0200 [gdb/testsuite] Add gdb.dwarf2/forward-spec-inter-cu.exp Add a regression test for PR symtab/30846. Tested on x86_64-linux. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30846 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-16 17:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-13 14:32 [Bug symtab/30846] New: " vries at gcc dot gnu.org 2023-10-02 12:54 ` [Bug symtab/30846] " vries at gcc dot gnu.org 2024-01-18 15:41 ` tromey at sourceware dot org 2024-02-09 19:42 ` tromey at sourceware dot org 2024-04-16 17:55 ` cvs-commit at gcc dot gnu.org 2024-04-16 17:55 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-16 17:55 ` cvs-commit at gcc dot gnu.org 2024-04-16 17:57 ` 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-30846-4717-1prEJ4LOtI@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).