From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id BA9BF3858D20 for ; Mon, 11 Mar 2024 15:38:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BA9BF3858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark.ca ARC-Filter: OpenARC Filter v1.0.0 sourceware.org BA9BF3858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=158.69.221.121 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710171519; cv=none; b=wvKfJgTO/6yssbwnP61nEBDWAdcqUEH2b+1aHHWtNRXY8oSWjWmmqJq+xA/0Gv9sO616ffCMvZDqyOS2yMxb+TUgYC6Cv7oUv2PNU8aUoHh8A5vnhBIZK7WzhK4WxIrb4mdrL14FjnnNL9IyilDrinFDRzwxQpbKQuy/XBivafk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1710171519; c=relaxed/simple; bh=GN85Jb3nRmAvvc/04btYCkaMSe9IlqKzeoCP2aTFfVc=; h=DKIM-Signature:Message-ID:Date:MIME-Version:Subject:To:From; b=Y4LZ8ldJUVcoll1GIU5NH5NS9BbRgkckmFOuYk1Xi0BlWmxz2hQUGZORKYHtGodHxnSvE2ufWbORx8NQ6W7S3jIrd0eeLVCz/zWtrR2pCAwIX14TGEk32obMijFCe+xsankIbGlO+nGCFuvsfEO3tj3p6lmp+517BTblq2QMQys= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1710171517; bh=GN85Jb3nRmAvvc/04btYCkaMSe9IlqKzeoCP2aTFfVc=; h=Date:Subject:To:References:From:In-Reply-To:From; b=X/4QZg5lcB3C7tmYqLrMo5cINXROSKmHkh/U8VMXdO49KpkF1vipVm6++f4TtkGCs GVoYJqOI3zWyBU2Qyv/tfaEdWbNfLR+XgucfSQBIelkkqLApGBUUuO6SDX2WaRvGsT 0CBch9cNxDa/S8iOINvV6CHQ/3zKlhB6JGanmrY8= Received: from [172.16.0.192] (192-222-143-198.qc.cable.ebox.net [192.222.143.198]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 2B0221E0AC; Mon, 11 Mar 2024 11:38:37 -0400 (EDT) Message-ID: Date: Mon, 11 Mar 2024 11:38:36 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Windows debugger -> gdbserver throws up a weird error Content-Language: fr To: Dilip Ranganathan , gdb@sourceware.org References: From: Simon Marchi In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 3/6/24 20:58, Dilip Ranganathan via Gdb wrote: > Recently Microsoft advertised > > their ability to connect their Windbg debugger to gdbserver running on a > remote machine through WSL. I have been trying to experiment with that. I > ssh into a linux machine through WSL. When I try to connect using Windbg, > the connection is successfully established but gdbserver dies with: > > ../../gdbserver/regcache.cc:271: A problem internal to GDBserver has been > detected. > Unknown register ymm0h requested > > A bit of searching on the interwebs revealed this to be a problem with a > particular version of gdbserver (< 7.0) but I am running the latest (14.2), > so it probably isn't a version issue. > > Interestingly I am successfully able to connect from yet another linux > machine from gdb to gdbserver just fine. > > Any ideas on why or how this might have happened? Windbg must do something different than GDB, causing GDBserver to take a different (and obviously less tested) path. Can you run gdbserver with `--debug=remote`? It will show all the communication between it and GDB / Windbg. For instance: $ gdbserver --debug=remote localhost:1234 python3 Do a run with GDB and one with Windbg. You can open a bug at https://sourceware.org/bugzilla and attach files with the output of both runs there. Thanks, Simon