public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: gcc-patches@gcc.gnu.org, Ian Lance Taylor <ian@airs.com>
Subject: Re: [RFC 0/2] libbacktrace: add FDPIC support
Date: Mon, 27 May 2024 00:12:54 -0700	[thread overview]
Message-ID: <CAMo8Bf+Nc2PTn1s38qoMQDc4k+W8+a+x9HrD9+PkZg4kTpFBTw@mail.gmail.com> (raw)
In-Reply-To: <yddttijg2mk.fsf@CeBiTec.Uni-Bielefeld.DE>

On Mon, May 27, 2024 at 12:01 AM Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
> > 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?
>
> it doesn't ;-(  See PR libstdc++/111641 for details.  There's a patch in
> there, too.

Oh, cool, thanks for the pointer Rainer. So patch 2 of this series can be
disregarded.

-- 
Thanks.
-- Max

      reply	other threads:[~2024-05-27  7:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  6:50 Max Filippov
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 [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=CAMo8Bf+Nc2PTn1s38qoMQDc4k+W8+a+x9HrD9+PkZg4kTpFBTw@mail.gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ian@airs.com \
    --cc=ro@cebitec.uni-bielefeld.de \
    /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).