public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/26683] New: FAIL: gdb.base/info-types-c++.exp: info types Date: Wed, 30 Sep 2020 14:10:05 +0000 [thread overview] Message-ID: <bug-26683-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26683 Bug ID: 26683 Summary: FAIL: gdb.base/info-types-c++.exp: info types Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With current trunk (at commit e37c930f9e "gcc-4.4.7 warning fixes"), I see: ... FAIL: gdb.base/info-types-c++.exp: info types ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-09-30 14:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-30 14:10 vries at gcc dot gnu.org [this message] 2020-09-30 14:51 ` [Bug gdb/26683] " vries at gcc dot gnu.org 2020-09-30 15:05 ` vries at gcc dot gnu.org 2020-09-30 15:10 ` vries at gcc dot gnu.org 2020-09-30 15:48 ` vries at gcc dot gnu.org 2020-09-30 17:05 ` tromey at sourceware dot org 2020-09-30 19:47 ` [Bug symtab/26683] " vries at gcc dot gnu.org 2020-09-30 19:49 ` cvs-commit at gcc dot gnu.org 2020-09-30 19:49 ` vries at gcc dot gnu.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-26683-4717@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).