From: Indu Bhagat <indu.bhagat@oracle.com>
To: Florian Weimer <fweimer@redhat.com>,
Indu Bhagat via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf.h: add PT_GNU_SFRAME
Date: Wed, 22 Feb 2023 14:21:39 -0800 [thread overview]
Message-ID: <27b12c33-dcac-a2e8-8349-b4fd094ba676@oracle.com> (raw)
In-Reply-To: <87zgag0z2m.fsf@oldenburg.str.redhat.com>
On 1/18/23 05:09, Florian Weimer wrote:
> * Indu Bhagat via Libc-alpha:
>
>> Support for SFrame format is available in Binutils 2.40. The GNU ld merges
>> the input .sframe sections and creates an output .sframe section in a
>> segment PT_GNU_SFRAME.
>> ---
>> elf/elf.h | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/elf/elf.h b/elf/elf.h
>> index b6a75c13a8..9692200f6f 100644
>> --- a/elf/elf.h
>> +++ b/elf/elf.h
>> @@ -728,6 +728,7 @@ typedef struct
>> #define PT_GNU_STACK 0x6474e551 /* Indicates stack executability */
>> #define PT_GNU_RELRO 0x6474e552 /* Read-only after relocation */
>> #define PT_GNU_PROPERTY 0x6474e553 /* GNU property */
>> +#define PT_GNU_SFRAME 0x6474e554 /* SFrame segment. */
>> #define PT_LOSUNW 0x6ffffffa
>> #define PT_SUNWBSS 0x6ffffffa /* Sun Specific segment */
>> #define PT_SUNWSTACK 0x6ffffffb /* Stack segment */
>
> Please submit this to the gnu-gabi list as well, preferably with a
> documentation patch.
>
Thanks. A patch was posted to gnu-gabi
https://sourceware.org/pipermail/gnu-gabi/2023q1/000522.html
(BTW, on the Binutils side, the patch to update documentation to use
"stack trace" instead of "unwind" for SFrame, has been committed).
Thanks
Indu
> Thanks,
> Florian
>
next prev parent reply other threads:[~2023-02-22 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 6:41 Indu Bhagat
2023-01-18 13:09 ` Florian Weimer
2023-02-22 22:21 ` Indu Bhagat [this message]
2023-04-28 9:15 ` Florian Weimer
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=27b12c33-dcac-a2e8-8349-b4fd094ba676@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).