public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Walt Drummond via Gdb <gdb@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>,  Walt Drummond <walt@drummond.us>
Subject: Re: AMD64_LINUX_frame_size
Date: Mon, 11 Jan 2021 11:43:05 +0100	[thread overview]
Message-ID: <87sg77pxdy.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CADCN6nzB1Sn=8200TfpSSbKgBoGJFc35_PtpFd5vfkg7G1uuyw@mail.gmail.com> (Walt Drummond via Gdb's message of "Thu, 7 Jan 2021 13:49:50 -0800")

* Walt Drummond via Gdb:

> Thanks Tom.  My math shows the kernel sizes as
> Redzone 128
> math frame/xstate 840
> rt_sigframe 456
>
> That's a total of 1424 bytes, so maybe GDB is saving less than it should?

With AVX-512, the kernel size is way larger.

Do you know for what purpose GDB needs this information?  Decoding the
xstate is quite complicated as far as I know.  Is it related to
preserving stack contents across signal delivery?

Thanks,
Florian
-- 
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill


  parent reply	other threads:[~2021-01-11 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 18:30 AMD64_LINUX_frame_size Walt Drummond
2021-01-06 16:38 ` AMD64_LINUX_frame_size Walt Drummond
2021-01-07 21:19   ` AMD64_LINUX_frame_size Tom Tromey
2021-01-07 21:49     ` AMD64_LINUX_frame_size Walt Drummond
2021-01-09 20:14       ` AMD64_LINUX_frame_size Tom Tromey
2021-01-11 10:43       ` Florian Weimer [this message]
2021-01-12 16:10         ` AMD64_LINUX_frame_size Walt Drummond

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=87sg77pxdy.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=tom@tromey.com \
    --cc=walt@drummond.us \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).