Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Florian Weimer via Gdb <gdb@sourceware.org>
To: Peter Bergner via Libc-help <libc-help@sourceware.org>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	 Sachin Monga <smonga@linux.ibm.com>,
	 "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	 gdb@sourceware.org,  Peter Bergner <bergner@tenstorrent.com>,
	 Segher Boessenkool <segher@kernel.crashing.org>,
	 Michael Meissner <meissner@linux.ibm.com>,
	Surya Kumari Jangala <jskumari@linux.ibm.com>,
	 Carl Love <cel@linux.ibm.com>
Subject: Re: [EXT] Re: gdb does not stop at printf for ppc
Date: Thu, 02 Oct 2025 18:58:46 +0200	[thread overview]
Message-ID: <lhuldltfdfd.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <d0e6a644-bac1-4727-90cc-b60f209aea13@tenstorrent.com> (Peter Bergner via Libc-help's message of "Thu, 2 Oct 2025 10:57:22 -0500")

* Peter Bergner via Libc-help:

> Ok, it's an even bigger problem than we thought.  I'm surprised no one
> else has hit this before us.

We've encountered it with fortification and IFUNC resolvers.  It used to
be considered a user error.

> Ok, this is promising and yeah, is what Carl and Uli suggested.
> That said, their comment from the bugzilla:
>
>     The new redirected symbols need to be dynamic symbols in case only
>     the stripped binary is available.

I'd recommend distributions do not strip .symtab on libc.so.6.  I don't
think making this a dynamic symbol is worth it.  It would have to be a
compatibility symbol under a separate symbol version, one for each
variant alias (eight for POWER?).  This is quite a bit of complexity.

Thanks,
Florian


  parent reply	other threads:[~2025-10-02 17:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f4e905f7-48cb-439a-a8e6-a50242c18e6a@linux.ibm.com>
2025-10-01  4:03 ` Peter Bergner via Gdb
2025-10-01 17:20   ` Adhemerval Zanella Netto via Gdb
2025-10-02 15:57     ` [EXT] " Peter Bergner via Gdb
2025-10-02 16:19       ` Carl Love via Gdb
2025-10-02 16:58       ` Florian Weimer via Gdb [this message]
2025-10-02 18:12         ` Peter Bergner via Gdb
2025-10-02 18:49           ` Billie Alsup (balsup) via Gdb
2025-10-02 19:09             ` Peter Bergner via Gdb
2025-10-03 19:43     ` Tom Tromey
2025-10-07 17:21       ` Adhemerval Zanella Netto via Gdb
2025-10-15 14:33         ` [EXT] " Peter Bergner via Gdb
2025-10-15 17:09           ` Sachin Monga via Gdb
2025-11-05  6:00             ` Sachin Monga via Gdb
2025-11-06  4:13               ` Peter Bergner via Gdb

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=lhuldltfdfd.fsf@oldenburg.str.redhat.com \
    --to=gdb@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=bergner@tenstorrent.com \
    --cc=cel@linux.ibm.com \
    --cc=fweimer@redhat.com \
    --cc=jskumari@linux.ibm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-help@sourceware.org \
    --cc=meissner@linux.ibm.com \
    --cc=segher@kernel.crashing.org \
    --cc=smonga@linux.ibm.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