public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jhb at FreeBSD dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/30912] Regression: make check TESTS="gdb.base/gcore.exp" RUNTESTFLAGS="--target_board=native-extended-gdbserver" Date: Mon, 20 Nov 2023 23:59:22 +0000 [thread overview] Message-ID: <bug-30912-4717-scVhZKTnTA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30912-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30912 jhb at FreeBSD dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb at FreeBSD dot org --- Comment #5 from jhb at FreeBSD dot org --- Sorry I didn't see this earlier for some reason, yes, this is related to the fact that when using gdbserver, GDB doesn't know what layout to use when writing out a core dump. The long term solution is to pull the CPUID info from gdbserver in the form of NT_X86_CPUID, but in the short term we could just always use the Intel layout that GDB assumed before the XSAVE series. That is, we could pick a default layout based on the XCR0 mask that corresponds to one of the known sizes and use that to set both the layout and size. I'll see if I can't come up with a variant of that today or tomorrow. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-20 23:59 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-28 16:53 [Bug gdb/30912] New: " simon.marchi at polymtl dot ca 2023-09-28 17:40 ` [Bug gdb/30912] " brobecker at gnat dot com 2023-09-28 18:45 ` brobecker at gnat dot com 2023-10-28 15:54 ` brobecker at gnat dot com 2023-10-28 19:36 ` simark at simark dot ca 2023-11-20 23:59 ` jhb at FreeBSD dot org [this message] 2023-11-22 20:56 ` jhb at FreeBSD dot org 2023-11-27 21:53 ` cvs-commit at gcc dot gnu.org 2023-11-27 22:00 ` cvs-commit at gcc dot gnu.org 2023-11-27 22:01 ` jhb at FreeBSD 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-30912-4717-scVhZKTnTA@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).