[Bug record/30169] FAIL: gdb.btrace/reconnect.exp: first: info record

["markus.t.metzger at intel dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30169

--- Comment #4 from Markus Metzger <markus.t.metzger at intel dot com> ---
(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 ?
> 
> 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 <tom@tromey.com>
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

-- 
You are receiving this mail because:
You are on the CC list for the bug.