public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jcmvbkbc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042
Date: Sat, 04 May 2024 08:35:52 +0000 [thread overview]
Message-ID: <bug-114941-4-p6mbO5ERjv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114941-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114941
--- Comment #3 from jcmvbkbc at gcc dot gnu.org ---
(In reply to Ian Lance Taylor from comment #2)
> What is the correct way to get the address at which the shared library was
> loaded when using FDPIC?
There's no single base address in case of FDPIC, the macro __RELOC_POINTER(ptr,
loadaddr) can be used with the elf32_fdpic_loadaddr::dlpi_addr as the last
argument to translate an address according to the load map. An example is
available in the libgcc/unwind-dw2-fde-dip.c
next prev parent reply other threads:[~2024-05-04 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 20:08 [Bug libbacktrace/114941] New: libbacktrace build is broken for FDPIC uclibc targets by gcc-14-5173-g2b64e4a54042 jcmvbkbc at gcc dot gnu.org
2024-05-03 20:14 ` [Bug libbacktrace/114941] libbacktrace build is broken for FDPIC uclibc targets by r14-5173-g2b64e4a54042 pinskia at gcc dot gnu.org
2024-05-03 22:37 ` ian at airs dot com
2024-05-04 8:35 ` jcmvbkbc at gcc dot gnu.org [this message]
2024-05-27 7:17 ` jcmvbkbc at gcc dot gnu.org
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=bug-114941-4-p6mbO5ERjv@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).