From: "Joos, Christina" <christina.joos@intel.com>
To: Andrew Burgess <aburgess@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Rohr, Stephan" <stephan.rohr@intel.com>
Subject: RE: [PATCH v2 1/1] gdb: Enable OS generated corefiles on systems with Intel AMX support.
Date: Mon, 21 Sep 2026 07:51:01 +0000 [thread overview]
Message-ID: <SN7PR11MB763889147C0993348AFA5D0689842@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87y0cxa21o.fsf@redhat.com>
> -----Original Message-----
> From: Andrew Burgess <aburgess@redhat.com>
> Sent: Samstag, 19. September 2026 13:55
> To: Joos, Christina <christina.joos@intel.com>; gdb-patches@sourceware.org
> Cc: Rohr, Stephan <stephan.rohr@intel.com>
> Subject: Re: [PATCH v2 1/1] gdb: Enable OS generated corefiles on systems with
> Intel AMX support.
>
> Christina Joos <christina.joos@intel.com> writes:
>
> > This patch addresses the issue described in PR gdb/34561. On systems
> > with Intel AMX support the xsave size is 11008. This xsave size is
> > not handled by gdb/i387-tdep.c:i387_guess_xsave_layout and is causing
> > problems for corefiles generated by the linux kernel. The problem is
> > visible regardless of the AMX enablement state in the dumping process,
> > so all corefiles on newer systems with AMX are broken.
Hi Andrew,
Thanks a lot for pushing this patch.
> FYI: https://sourceware.org/bugzilla/show_bug.cgi?id=34646
> Could you take a look if you have a chance please.
As described in the discussion for v1 of this patch [1], the issue described in the bug
34646, just became visible due to the improved test coverage for core files, which
are also part of this patch.
They are unrelated to the GDB code changes of this patch, so the issue existed before,
too. I added a comment in the bug, so this is hopefully clearer now.
[1] https://sourceware.org/pipermail/gdb-patches/2026-September/230279.html
Kind Regards,
Christina
________________________________________
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 (89) 99143-0
www.intel.de
Managing Directors: Candice Moore, Jeffrey Schneiderman, Ramachandran Sitaraman
Chairperson of the Supervisory Board: Sonja Pierer
Registered Seat: Munich Commercial Register B: Amtsgericht Munich HRB 186928
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2026-09-21 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 16:30 Christina Joos
2026-09-15 15:06 ` Andrew Burgess
2026-09-19 11:55 ` Andrew Burgess
2026-09-21 7:51 ` Joos, Christina [this message]
2026-09-21 10:04 ` Andrew Burgess
2026-09-21 13:17 ` Joos, Christina
2026-09-24 13:11 ` Andrew Burgess
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=SN7PR11MB763889147C0993348AFA5D0689842@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=christina.joos@intel.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=stephan.rohr@intel.com \
/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