public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "wmessmer at microsoft dot com" <sourceware-bugzilla@sourceware.org> 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 [thread overview] Message-ID: <bug-31526-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31526 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 processes 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:" packet without "xmlRegisters=..." after having sent one with "xmlRegisters=aarch64,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 of a target description without AVX registers. The next time the plug-in sends a packet across the RSP which involves register state read, gdbserver attempts to read AVX registers and faults with the internal error because the target description does not contain them. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-21 23:31 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-21 23:31 wmessmer at microsoft dot com [this message] 2024-04-02 1:53 ` [Bug server/31526] " tromey at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31526-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).