From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B73673858D39; Mon, 27 Feb 2023 13:32:52 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B73673858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1677504772; bh=By/I3tySwcDUl2HgLcDA+anpxlw1owMV6biIx8UdJ9I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=sUS9uA0cDJ9KSlwyqNN0sJUVap6BOlgFobC1s+cIGA5RF9pwNQgC+fBSrVsUSxgQG GA5X2xixDT1gi7kDy9Jkq4erxWnVsNU9InslyY5A+1O4EFQxdggbLr1vwDSnia1mS8 B/BXTR0dmqjRLq4Ds3Xx8haqWsIXeSo6VkdKCJqA= From: "markus.t.metzger at intel dot com" To: gdb-prs@sourceware.org Subject: [Bug record/30169] FAIL: gdb.btrace/reconnect.exp: first: info record Date: Mon, 27 Feb 2023 13:32:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed 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: markus.t.metzger at intel dot com 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: Message-ID: In-Reply-To: References: 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 --- Comment #4 from Markus Metzger --- (In reply to Markus Metzger from comment #3) > (In reply to Tom de Vries from comment #1) > > Is this another instance of the problem we've added xfailing for in > > gdb.python/py-record-btrace.exp ? >=20 > Doesn't look related to me. This one is about parsing the XML. I can > reproduce it on my system. Looks like a regression to me. Bisecting... 873a185be258ad2552b9579005852815b4da5baf is the first bad commit commit 873a185be258ad2552b9579005852815b4da5baf Author: Tom Tromey Date: Fri Dec 16 07:56:57 2022 -0700 Don't use struct buffer in handle_qxfer_btrace This changes handle_qxfer_btrace and handle_qxfer_btrace_conf, in gdbserver, to use std::string rather than struct buffer. gdbserver/linux-low.cc | 72 +++++++++++++++++++++++++---------------------= ---- gdbserver/linux-low.h | 4 +-- gdbserver/server.cc | 32 +++++++++++----------- gdbserver/target.cc | 6 ++--- gdbserver/target.h | 9 +++---- 5 files changed, 61 insertions(+), 62 deletions(-) bisect found first bad commit --=20 You are receiving this mail because: You are on the CC list for the bug.=