Re: AMD64_LINUX_frame_size

Walt Drummond via Gdb <[email protected]>
Newsgroups gmane.comp.gdb.devel
Message-ID <CADCN6nwezBw4VyXPcdFe5E-hpcknYt7jF8F_g=h9tTO34qd46A@mail.gmail.com>
I haven't been able to get a handle on this yet.  Part of the problem
is that I can't construct a test case w/out hitting the "Process
record does not support instruction 0xc5 at address 0xblah..." issue,
and I haven't found a workaround yet.

On Mon, Jan 11, 2021 at 2:43 AM Florian Weimer <[email protected]> wrote:
>
> * 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
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.