From: Vignesh Balasubramanian <vigbalas@amd.com>
To: <gdb-patches@sourceware.org>, <jinisusan.george@amd.com>,
<christina.schimpe@intel.com>, <AlokKumar.Sharma@amd.com>,
<jhb@FreeBSD.org>, <simark@simark.ca>
Cc: Vignesh Balasubramanian <vigbalas@amd.com>
Subject: [PATCH 32 0/2] Handle the new .note section introduced in Linux
Date: Mon, 8 Dec 2025 14:08:17 +0530 [thread overview]
Message-ID: <20251208083819.2560894-1-vigbalas@amd.com> (raw)
The XSAVE layout of the machine where the core file is dumped is not visible
to GDB. It is assumed currently using some heuristics.
It has been addressed to some extent recently but still uses heuristics.
https://inbox.sourceware.org/gdb-patches/2628f45a-77f7-8b2c-20aa-da65d1d82a37@simark.ca/T/#m4c67d59c18a5962f771ba8ca1e2bee9365ad1ab2
New patches have been committed to the linux kernel (version 6.12) to resolve
this issue by adding a new .note section which contains descriptions of the
xsave layout to the core file.
The first of this patch set consumes this new .note section and uses that to
identify the xsave layout.
The second one enables gdb to generate a similar .note section if the corefile
is dumped through the 'gcore' command.
Working on test case patch, will share it in a few days.
This patch shoud be applied on top of binutils patch: https://sourceware.org/pipermail/binutils/2025-September/144207.html
Co-Authored-By: Jini Susan George <jinisusan.george@amd.com>
Vignesh Balasubramanian (2):
core: Consume the new .note section that contains descriptions of
xsave layout
gcore: Create a new .note section for x86
gdb/amd64-linux-tdep.c | 2 +-
gdb/gcore-elf.c | 18 ++++++++
gdb/gcore-elf.h | 8 ++++
gdb/i386-linux-tdep.c | 25 ++++++++---
gdb/i386-linux-tdep.h | 3 +-
gdb/i387-tdep.c | 86 ++++++++++++++++++++++++++++++++++++++
gdb/i387-tdep.h | 12 ++++++
gdb/linux-tdep.c | 1 +
gdb/nat/x86-xstate.c | 31 ++++++++++++++
gdb/nat/x86-xstate.h | 6 +++
gdb/target-debug.h | 6 +++
gdb/target-delegates-gen.c | 26 ++++++++++++
gdb/target.c | 5 +++
gdb/target.h | 10 +++++
gdb/x86-linux-nat.c | 6 +++
gdb/x86-linux-nat.h | 1 +
gdbsupport/x86-xstate.h | 6 +++
17 files changed, 244 insertions(+), 8 deletions(-)
--
2.34.1
next reply other threads:[~2025-12-08 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 8:38 Vignesh Balasubramanian [this message]
2025-12-08 8:38 ` [PATCH 32 1/2] core: Consume the new .note section that contains descriptions of xsave layout Vignesh Balasubramanian
2025-12-08 8:38 ` [PATCH 32 2/2] gcore: Create a new .note section for x86 Vignesh Balasubramanian
2025-12-14 13:39 ` [PATCH 32 0/2] Handle the new .note section introduced in Linux Schimpe, Christina
2026-01-06 6:48 ` Balasubrmanian, Vignesh
2026-03-06 7:08 ` Schimpe, Christina
2026-03-06 7:42 ` Balasubrmanian, Vignesh
2026-03-06 8:13 ` Schimpe, Christina
2026-03-11 9:50 ` Schimpe, Christina
2026-03-13 14:08 ` Schimpe, Christina
2026-03-17 10:02 ` Schimpe, Christina
2026-02-08 4:18 ` Vignesh Balasubramanian
2026-03-16 12:59 ` [PATCH 32 0/2] Handle the new .note section introduced in Linux Schimpe, Christina
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=20251208083819.2560894-1-vigbalas@amd.com \
--to=vigbalas@amd.com \
--cc=AlokKumar.Sharma@amd.com \
--cc=christina.schimpe@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=jinisusan.george@amd.com \
--cc=simark@simark.ca \
/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: link
Be 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