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 record/30169] FAIL: gdb.btrace/reconnect.exp: first: info record
Date: Sat, 25 Feb 2023 08:54:03 +0000 [thread overview]
Message-ID: <bug-30169-4717-Uf9gbkVMsO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30169-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30169
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markus.t.metzger at intel dot com
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Is this another instance of the problem we've added xfailing for in
gdb.python/py-record-btrace.exp ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-25 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 8:51 [Bug record/30169] New: " vries at gcc dot gnu.org
2023-02-25 8:54 ` vries at gcc dot gnu.org [this message]
2023-02-25 8:57 ` [Bug record/30169] " vries at gcc dot gnu.org
2023-02-27 12:20 ` markus.t.metzger at intel dot com
2023-02-27 13:32 ` markus.t.metzger at intel dot com
2023-02-28 7:59 ` vries at gcc dot gnu.org
2023-02-28 23:35 ` tromey at sourceware dot org
2023-03-01 1:32 ` tromey at sourceware dot org
2023-03-01 1:41 ` tromey at sourceware dot org
2023-03-01 1:47 ` tromey at sourceware dot org
2023-03-01 13:38 ` cvs-commit at gcc dot gnu.org
2023-03-01 13:39 ` 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-30169-4717-Uf9gbkVMsO@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).