From: Tom Tromey <tom@tromey.com>
To: Adhemerval Zanella Netto via Gdb <gdb@sourceware.org>
Cc: Peter Bergner <bergner@tenstorrent.com>,
Sachin Monga <smonga@linux.ibm.com>,
libc-help@sourceware.org,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Michael Meissner <meissner@linux.ibm.com>,
Surya Kumari Jangala <jskumari@linux.ibm.com>,
Carl Love <cel@us.ibm.com>
Subject: Re: gdb does not stop at printf for ppc
Date: Fri, 03 Oct 2025 13:43:55 -0600 [thread overview]
Message-ID: <87wm5b6a9w.fsf@tromey.com> (raw)
In-Reply-To: <0535055f-7a42-4390-b134-34b8e3ee657e@linaro.org> (Adhemerval Zanella Netto via Gdb's message of "Wed, 1 Oct 2025 14:20:11 -0300")
>>>>> Adhemerval Zanella Netto via Gdb <gdb@sourceware.org> writes:
I didn't really follow this discussion, but:
> Do we have the concept of symbol aliases for DWARF?
Yes, DWARF can use DW_TAG_imported_declaration. However gdb's support
for this is incomplete and you'd have to try it out to see if it's
sufficient for this purpose.
Tom
next prev parent reply other threads:[~2025-10-03 19:45 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
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 [this message]
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=87wm5b6a9w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=adhemerval.zanella@linaro.org \
--cc=bergner@tenstorrent.com \
--cc=cel@us.ibm.com \
--cc=gdb@sourceware.org \
--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