From: Max Filippov <jcmvbkbc@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: Ian Lance Taylor <ian@airs.com>, Max Filippov <jcmvbkbc@gmail.com>
Subject: [RFC 0/2] libbacktrace: add FDPIC support
Date: Sun, 26 May 2024 23:50:24 -0700 [thread overview]
Message-ID: <20240527065026.855607-1-jcmvbkbc@gmail.com> (raw)
This is an RFC series that adds FDPIC ELF target support to
libbacktrace.
While debugging this I've noticed that there's no unwinding info for the
libstdc++ version of libbacktrace, which made backtraces empty for me,
both on xtensa-linux-uclibcfdpic and on regular xtensa-linux-uclibc.
Adding -funwind-tables to the libstdc++ version of libbacktrace fixed
that. Which makes me wonder how it works for other architectures?
Max Filippov (2):
libbacktrace: add FDPIC support
libstdc++-v3/src/libbacktrace: add -funwind-tables
libbacktrace/dwarf.c | 60 ++++++++++++++---------
libbacktrace/elf.c | 20 +++++---
libbacktrace/internal.h | 14 +++++-
libstdc++-v3/src/libbacktrace/Makefile.am | 4 +-
libstdc++-v3/src/libbacktrace/Makefile.in | 4 +-
5 files changed, 66 insertions(+), 36 deletions(-)
--
2.39.2
next reply other threads:[~2024-05-27 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 6:50 Max Filippov [this message]
2024-05-27 6:50 ` [RFC 1/2] " Max Filippov
2024-06-11 16:54 ` Max Filippov
2024-05-27 6:50 ` [RFC 2/2] libstdc++-v3/src/libbacktrace: add -funwind-tables Max Filippov
2024-05-27 7:01 ` [RFC 0/2] libbacktrace: add FDPIC support Rainer Orth
2024-05-27 7:12 ` Max Filippov
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=20240527065026.855607-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.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).