From: Florian Weimer <fweimer@redhat.com>
To: Abhijit Ray Chaudhury via Libc-help <libc-help@sourceware.org>
Cc: Abhijit Ray Chaudhury <abhijit.ray.chaudhury@gmail.com>
Subject: Re: Does glibc support remote process backtracing
Date: Mon, 27 Nov 2023 10:20:02 +0100 [thread overview]
Message-ID: <87o7ffpn7h.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAACKNgUkX9SHC9YHmeE016YeSPcTFMo4t0VgENk6r3jYx6Z7Gg@mail.gmail.com> (Abhijit Ray Chaudhury via Libc-help's message of "Sat, 25 Nov 2023 11:32:30 +0530")
* Abhijit Ray Chaudhury via Libc-help:
> Hi,
> Libunwind supports remote process backtracing through libunwind-ptrace (
> https://www.nongnu.org/libunwind/man/libunwind-ptrace(3).html ). Does glibc
> also support remote process backtracing ?
For current architectures, glibc does not supply an implementation of
stack unwinding/backtrace generatio. We use libgcc_s for that (via the
unwind-link facility in glibc). There's no remote backtracing support
in libgcc_s.
There's a remote backtrace implementation in elfutils, which probably
has a greater affinity with the GNU toolchain on Linux (compared to
libunwind).
Thanks,
Florian
next prev parent reply other threads:[~2023-11-27 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 6:02 Abhijit Ray Chaudhury
2023-11-27 9:20 ` Florian Weimer [this message]
2023-11-28 7:35 ` Abhijit Ray Chaudhury
2023-12-11 9:14 ` Florian Weimer
2023-12-11 15:50 ` Szabolcs Nagy
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=87o7ffpn7h.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=abhijit.ray.chaudhury@gmail.com \
--cc=libc-help@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).