From: Indu Bhagat <indu.bhagat@oracle.com>
To: gnu-gabi@sourceware.org
Subject: Re: [PATCH,V2 0/1] Add PT_GNU_SFRAME segment
Date: Wed, 29 Mar 2023 11:43:44 -0700 [thread overview]
Message-ID: <b855ba17-934b-ae35-62fb-3ed28b3d8e1b@oracle.com> (raw)
In-Reply-To: <fa132691-8599-f882-b492-6959cee2155a@oracle.com>
On 2/2/23 01:00, Indu Bhagat wrote:
> On 1/24/23 21:59, Indu Bhagat wrote:
>> Hello,
>>
>> I've made the changes to reflect that the SFrame format is for
>> generating stack
>> traces only (and not for unwinding) to the GNU gabi proposed patch.
>>
>> I've also made the necessary documentation (code comments, doc files)
>> changes
>> in binutils (to be posted there soon). These changes, however, will be
>> available in the next GNU Binutils release.
>>
>> Thanks,
>>
>> Indu Bhagat (1):
>> Add PT_GNU_SFRAME segment
>>
>> program-loading-and-dynamic-linking.txt | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
> Hello,
>
> What are the next steps for this patch ?
>
> Thanks
> Indu
PING
prev parent reply other threads:[~2023-03-29 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 5:59 Indu Bhagat
2023-01-25 5:59 ` [PATCH,V2 1/1] " Indu Bhagat
2023-04-28 8:16 ` Florian Weimer
2023-02-02 9:00 ` [PATCH,V2 0/1] " Indu Bhagat
2023-03-29 18:43 ` Indu Bhagat [this message]
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=b855ba17-934b-ae35-62fb-3ed28b3d8e1b@oracle.com \
--to=indu.bhagat@oracle.com \
--cc=gnu-gabi@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).