From: Walt Drummond <walt@drummond.us>
To: gdb@sourceware.org
Subject: Re: AMD64_LINUX_frame_size
Date: Wed, 6 Jan 2021 08:38:59 -0800 [thread overview]
Message-ID: <CADCN6nxVYmjS+D0VX5-DqRTvf-Xc-EjN7cJ1vRyehg+vV6tVig@mail.gmail.com> (raw)
In-Reply-To: <CADCN6nyZB1XE9-UvyEEX2=EXOhAf9qRBDtPLoxuLt3xVF8otCQ@mail.gmail.com>
After looking at this further, I think I understand AMD64_LINUX_frame_size
and why it differs from the size of the kernel's rt_sigframe (differences
between glibc's and the kernels' definition of sigset_t), but I don't
understand how GDB arrived at 512 for AMD_LINUX_xstate. The kernel's math
frame, which also contains the extended state information, is 840 bytes. I
feel I must be missing something. Any pointers?
Thanks.
On Mon, Jan 4, 2021 at 10:30 AM Walt Drummond <walt@drummond.us> wrote:
> I'm trying to understand the relationship between the
> AMD64_LINUX_frame_size constant and the kernel's signal stack layout. Is
> there any documentation or commentary that describes how we got to the
> current value?
>
> Thanks.
>
>
next prev parent reply other threads:[~2021-01-06 16:39 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 ` Walt Drummond [this message]
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 ` AMD64_LINUX_frame_size Florian Weimer
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=CADCN6nxVYmjS+D0VX5-DqRTvf-Xc-EjN7cJ1vRyehg+vV6tVig@mail.gmail.com \
--to=walt@drummond.us \
--cc=gdb@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: 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).