From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id E81763858C1F; Tue, 28 Mar 2023 15:48:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E81763858C1F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1680018519;
	bh=6nvhZM00y3t9zFlDH+JthouaDcT8n58m0VtRwNlDahU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=sDfmIFGG4y0W0xenbTcVfVx6Tab45o6ub2fQAvrHAf1BQGMWkkadGRB0tMgVvbitd
	 J7T1BtKt8/YYFzYqkmJQm1cJie7pCOI/G/bPVLKE/NqHEeNPWwDSpthZ8woe7eOzX7
	 I+orAdBcM/LvNopdApoKYYibZzOeivHgBki31FdI=
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29734] [gdb/testsuite, local-remote-host-native]
 FAIL: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=off:
 to_disable=: set remote  threads-packet off (timeout)
Date: Tue, 28 Mar 2023 15:48:39 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit 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: 
Message-ID: <bug-29734-4717-jQz267kLOF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29734-4717@http.sourceware.org/bugzilla/>
References: <bug-29734-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

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

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gn=
u.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D9121a23fa729=
4542d022c25eda0fe8b9e92c3b59

commit 9121a23fa7294542d022c25eda0fe8b9e92c3b59
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Mar 28 17:48:34 2023 +0200

    [gdb/testsuite] Fix local-remote-host-native.exp for gdb.server tests

    When running test-case gdb.server/stop-reply-no-thread-multi.exp with
    host+target board local-remote-host-native, I run into a time-out:
    ...
    (gdb) PASS: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=
=3Doff:
\
      to_disable=3D: disconnect
    builtin_spawn /usr/bin/ssh -t -l vries 127.0.0.1 gdbserver --once \
      localhost:2346 stop-reply-no-thread-multi^M
    Process stop-reply-no-thread-multi created; pid =3D 32600^M
    Listening on port 2346^M
    set remote threads-packet off^M
    FAIL: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=3Doff:=
 \
      to_disable=3D: set remote threads-packet off (timeout)
    ...

    This is due to this line in ${board}_spawn:
    ...
        set board_info($board,fileid) $spawn_id
    ...

    We have the following series of events:
    - gdb is spawned, setting fileid
    - a few gdb commands (set height etc) are send using fileid, arrive at =
gdb
and
      are successful
    - gdbserver is spawned, overwriting fileid
    - the next gdb command is sent using fileid, so it's send
      to gdbserver instead of gdb, and we run into the timeout.

    There is some notion of current gdb, tracked in both gdb_spawn_id and
fileid
    of the host board (see switch_gdb_spawn_id).  And because the host and
target
    board are the same, spawning something on the target overwrites the fil=
eid
on
    host, and consequently the current gdb.

    Fix this by only setting fileid when spawning gdb.

    Tested on x86_64-linux.

    Now gdb.server/*.exp passes for host+target board local-remote-host-nat=
ive,
    except for file-transfer.exp.

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29734

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