From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5AA393858D28; Thu, 21 Mar 2024 23:31:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5AA393858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1711063900; bh=Gh17spflJEBMpxRcuvl9uMZZXq2d6qf/iy2zs9sHkDg=; h=From:To:Subject:Date:From; b=AjVJ64QjVtM839bJymrf0oFCMC7cMAxnbrNjBoYD1F3Oi9MAeG8FEMXbUQf4PeL2J TLlh66YIyc8xbB7hrCJa4W5zFTJkZGhHWwBr0kwZn15kw8NSIldSk+8zzMlRZ0mRgj Ez1fiHKvxqxqnmmL9aqDZYPc9H5U1bb63CxKJzXM= From: "wmessmer at microsoft dot com" To: gdb-prs@sourceware.org Subject: [Bug server/31526] New: GDBServer crashes with an internal error cannot find "ymm0h" Date: Thu, 21 Mar 2024 23:31:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: 14.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wmessmer at microsoft dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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=3D31526 Bug ID: 31526 Summary: GDBServer crashes with an internal error cannot find "ymm0h" Product: gdb Version: 14.1 Status: UNCONFIRMED Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: wmessmer at microsoft dot com Target Milestone: --- WinDbg recently added support for connecting to and debugging Linux process= es via gdbserver. On gdbserver 12.1, the connection works fine. On gdbserver 14.x, the initial connection results in an immediate internal error in gdbserver claiming that it cannot find "ymm0h" Looking through things, it appears that this is caused by the WinDbg plug-in which provides this functionality inadvertently sending a "qSupported:" pac= ket without "xmlRegisters=3D..." after having sent one with "xmlRegisters=3Daarch64,i386". On 12.1, this clears x86_xcr0 of the AVX flag and causes utilization of a target description without AVX registers (which largely works fine). On 14= .x, this does NOT clear x86_xcr0 of the AVX flag but still causes utilization o= f a target description without AVX registers. The next time the plug-in sends a packet across the RSP which involves register state read, gdbserver attempt= s to read AVX registers and faults with the internal error because the target description does not contain them. --=20 You are receiving this mail because: You are on the CC list for the bug.=