From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 548933857C45; Sat, 25 Feb 2023 08:51:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 548933857C45 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1677315087; bh=CPMkwozYwgt+B3q5ryUjy5v/F1GX/68hHComnosWQko=; h=From:To:Subject:Date:From; b=OtXthqxFK7S2StYXATWUTux8PZ+8hEg7YPyw0hMDBD2H8NGy1a6HoNUxhsEPqsQn4 fkJCBYsRflP+d3e1afBt1s/aSRYO2leJh2J0bM9dsWLXDs0h7PsFbSGRDg9SVpDLC1 AG9fQgY74tIQBZwax53NWZxs/QGRpD5udCtcfaOY= From: "vries at gcc dot gnu.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 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30169 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=