From: Florian Weimer <fweimer@redhat.com>
To: Indu Bhagat via Gnu-gabi <gnu-gabi@sourceware.org>
Cc: Indu Bhagat <indu.bhagat@oracle.com>
Subject: Re: [PATCH,V2 1/1] Add PT_GNU_SFRAME segment
Date: Fri, 28 Apr 2023 10:16:32 +0200 [thread overview]
Message-ID: <87edo4bevz.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230125055916.1047754-2-indu.bhagat@oracle.com> (Indu Bhagat via Gnu-gabi's message of "Tue, 24 Jan 2023 21:59:16 -0800")
* Indu Bhagat via Gnu-gabi:
> ---
> program-loading-and-dynamic-linking.txt | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/program-loading-and-dynamic-linking.txt b/program-loading-and-dynamic-linking.txt
> index a07c195..ebf693e 100644
> --- a/program-loading-and-dynamic-linking.txt
> +++ b/program-loading-and-dynamic-linking.txt
> @@ -129,6 +129,20 @@ PT_GNU_PROPERTY 0x6474e553
>
> Reference: https://raw.githubusercontent.com/wiki/hjl-tools/linux-abi/linux-abi-draft.pdf
>
> +PT_GNU_SFRAME 0x6474e554
> +
> + Segment contains the SFrame section (Simple Frame format stack trace
> + information).
> +
> + NOTE: The virtual address range referred to by PT_GNU_SFRAME must be covered
> + by a PT_LOAD entry - PT_GNU_SFRAME on its own does not trigger the
> + mapping/loading of any data.
> +
> + The contents of the SFrame section are described in the GNU Binutils
> + documentation. As of 2.40:
> +
> + https://sourceware.org/binutils/docs/sframe-spec.html
> +
> There are further extensions to p_type but currently they are all
> architecture specific and should be documented in the relevant ABIs.
Thanks, pushed.
Florian
next prev parent reply other threads:[~2023-04-28 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 5:59 [PATCH,V2 0/1] " Indu Bhagat
2023-01-25 5:59 ` [PATCH,V2 1/1] " Indu Bhagat
2023-04-28 8:16 ` Florian Weimer [this message]
2023-02-02 9:00 ` [PATCH,V2 0/1] " Indu Bhagat
2023-03-29 18:43 ` Indu Bhagat
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=87edo4bevz.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=indu.bhagat@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).