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] New: FAIL: gdb.btrace/reconnect.exp: first: info record Date: Sat, 25 Feb 2023 08:51:27 +0000 [thread overview] Message-ID: <bug-30169-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30169 Bug ID: 30169 Summary: FAIL: gdb.btrace/reconnect.exp: first: info record Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: record Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- With current trunk, I ran into: ... (gdb) PASS: gdb.btrace/reconnect.exp: first: stepi 19 info record^M Active record target: record-btrace^M Recording format: Intel Processor Trace.^M Buffer size: 16kB.^M warning: while parsing btrace: not well-formed (invalid token)^M Error parsing branch trace.^M (gdb) FAIL: gdb.btrace/reconnect.exp: first: info record ... and: ... (gdb) info record^M Active record target: record-btrace^M Recording format: Intel Processor Trace.^M Buffer size: 16kB.^M warning: while parsing btrace: not well-formed (invalid token)^M Error parsing branch trace.^M (gdb) FAIL: gdb.btrace/reconnect.exp: second: info record ... I haven't tried to reproduce it yet. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-02-25 8:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-25 8:51 vries at gcc dot gnu.org [this message] 2023-02-25 8:54 ` [Bug record/30169] " vries at gcc dot gnu.org 2023-02-25 8:57 ` 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@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).