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 D00593858C53; Tue, 17 Jan 2023 16:28:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D00593858C53
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1673972901;
	bh=NfZ/OjUFflib7v7CrvxP32H79uruuuxPvIg5c1704wY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=k+wYpePVaHP60qDlLeToWKjFYVcKu16vBUOMIY6/Ckyq+p+pwDeUEU4MmYr5B9+ai
	 z60UfdfdygBgEodPsrc0LHRR6egTnMjUGuj4F3F5bwt12o7/Az5Xn/Uq5+0EmbjgyP
	 82gmq97rqHoVbdZJEORqUyul7mSN4tG82veX4KBU=
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/27927] gdb crash with OpenOCD
Date: Tue, 17 Jan 2023 16:28:20 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: remote
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey at sourceware dot 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: cc
Message-ID: <bug-27927-4717-021PlMGKGJ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-27927-4717@http.sourceware.org/bugzilla/>
References: <bug-27927-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=3D27927

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot o=
rg

--- Comment #14 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Simon Marchi from comment #12)

Looking at the trace:

>   [remote] Sending packet: $qXfer:threads:read::0,1000#92
>   [remote] Packet received: l<?xml version=3D"1.0"?>\n<threads>\n<thread
> id=3D"1">Name: Kernel's Stat Task, State: Delay, Priority: 6</thread>\n<t=
hread
> id=3D"2">Name: Wi-SUN MAC, State: Pend, Priority: 31</thread>\n<thread
> id=3D"3">Name: Wi-SUN Timer Task, State: Pend, Priority: 10</thread>\n<th=
read
> id=3D"4">Name: Wi-SUN Event Loop Task, State: Pend, Priority:
> 12</thread>\n<thread id=3D"5">Name: Wi-SUN RF Task, State: Pend, Priority:
> 9</thread>\n</threads>\n

This shows the threads, they have id 1-5.

>   [remote] Sending packet: $qC#b4
>   [remote] Packet received: QC0000000000000000

But the remote says that the current thread is 0, which seems
sort of nonsensical.  The docs say:

A THREAD-ID can
also be a literal '-1' to indicate all threads, or '0' to pick any
thread.

However, it seems to me that these special values do not make
sense for a QC response.

IOW, I think this is a bug in the remote stub.

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