From: Claudiu Zissulescu-Ianculescu <claudiu.zissulescu-ianculescu@oracle.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: toolchain-patches_ww_grp <toolchain-patches_ww_grp@oracle.com>,
libc-alpha@sourceware.org
Subject: SFrame stack tracer
Date: Wed, 9 Oct 2024 20:09:33 +0300 [thread overview]
Message-ID: <9bc1c439-b3f0-4833-9613-333eeffc629d@oracle.com> (raw)
Hi Florian,
I am comming back to you for clarifying some aspects of SFrame stack
tracer support in glibc.
Looking to dwarf stack unwinding support in glibc, it looks to me like
it is based on unwinder routines from libgcc.
Now, I would like to clarify if you would like to see the entire SFrame
stack tracer implementation added to glibc source code, i.e., without
any libgcc callbacks like in dwarf case.
As far as I can see, a SFrame stack tracer implementation will need some
architecture specific code added too, which may imply some extra
interfaces to be created on top of the suggested one in dl_find_object
structure.
Looking forward for your reaction, and thank you,
Claudiu
next reply other threads:[~2024-10-09 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 17:09 Claudiu Zissulescu-Ianculescu [this message]
2024-10-24 10:59 ` 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=9bc1c439-b3f0-4833-9613-333eeffc629d@oracle.com \
--to=claudiu.zissulescu-ianculescu@oracle.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=toolchain-patches_ww_grp@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).