From: Florian Weimer <fweimer@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Indu Bhagat <indu.bhagat@oracle.com>, gnu-gabi@sourceware.org
Subject: Re: [PATCH] Add PT_GNU_SFRAME segment
Date: Tue, 24 Jan 2023 14:20:23 +0100 [thread overview]
Message-ID: <87o7qof4rs.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <088fb3ea96e64f2dcc5e2af1d49bec3fdab3482a.camel@klomp.org> (Mark Wielaard's message of "Tue, 24 Jan 2023 12:13:44 +0100")
* Mark Wielaard:
> Hi Indu,
>
> On Mon, 2023-01-23 at 11:56 -0800, Indu Bhagat via Gnu-gabi wrote:
>> As I submit this patch, I am reminded of my ongoing unease with using the
>> keyword "unwind information" with SFrame format. SFrame format, is the Simple
>> Frame format, which represents the minimal necessary information for
>> backtracing:
>> - Canonical Frame Address (CFA)
>> - Frame Pointer (FP)
>> - Return Address (RA)
>> As such, one can argue that there is a clear distinction between "backtrace"
>> (=simple call trace) and "unwind"(=stack walk + recover state/regs).
>>
>> What do you think will the "correct" terminology here (if there is one) ?
>> Simple Frame format is for backtracing only, but calling it a "backtrace
>> format" also sounds off. May be "backtracing format" ? Simple Frame, SFrame,
>> backtracing format...
>>
>> Thoughts?
>
> What about calling it a "call trace"?
> Although technically it is a "return trace".
“Stack trace” matches “SFrame”. That's Python, Java etc. terminology
and seems appropriate here, too.
Thanks,
Florian
next prev parent reply other threads:[~2023-01-24 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 19:56 Indu Bhagat
2023-01-24 11:13 ` Mark Wielaard
2023-01-24 13:10 ` Carlos O'Donell
2023-01-24 13:20 ` Florian Weimer [this message]
2023-01-24 14:57 ` Carlos O'Donell
2023-01-24 21:52 ` 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=87o7qof4rs.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gnu-gabi@sourceware.org \
--cc=indu.bhagat@oracle.com \
--cc=mark@klomp.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).