public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marian.buschsieweke at posteo dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/31851] GDB ignores absolute function symbols
Date: Wed, 12 Jun 2024 11:11:17 +0000	[thread overview]
Message-ID: <bug-31851-4717-pvrfnQhUC3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31851-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31851

--- Comment #5 from Marian Buschsieweke <marian.buschsieweke at posteo dot net> ---
This is only anecdotally relevant to the bug, but may be of interest to some
reader anyway. I figured out why the functions became absolute symbols in the
first place.

Before, I claimed:

> There is no special handling of functions that end up as absolute symbols in either the C code or the linker script.

That turns out to be incorrect, in fact, the linker script explicitly placed
functions at absolute addresses. I overlooked this because this was not part of
the linker script of the application I looked at, but done by an external
linker script [1] of the vendor SDK I wasn't aware that it was included.

I guess for providing an ABI to a pre-compiled binary blob that needs to be
loaded at a given address, the use of absolute addresses does make sense :'(

[1]:
https://github.com/espressif/esp-idf/blob/24c20d188e24c815e28351cddb838c01e7dfb241/components/esp_rom/esp32/ld/esp32.rom.newlib-funcs.ld

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-06-12 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 12:35 [Bug gdb/31851] New: " marian.buschsieweke at posteo dot net
2024-06-06 13:50 ` [Bug gdb/31851] " marian.buschsieweke at posteo dot net
2024-06-06 13:51 ` marian.buschsieweke at posteo dot net
2024-06-11 21:38 ` marian.buschsieweke at posteo dot net
2024-06-11 21:45 ` marian.buschsieweke at posteo dot net
2024-06-12 11:11 ` marian.buschsieweke at posteo dot net [this message]
2024-06-12 12:40 ` tromey at sourceware dot 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-31851-4717-pvrfnQhUC3@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).