From: Ulrich Weigand <uweigand@de.ibm.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: fweimer@redhat.com, systemtap@sourceware.org,
sergiodj@sergiodj.net, doko@debian.org,
libc-alpha@sourceware.org, macro@orcam.me.uk
Subject: Re: GDB shared library tracking with stap probes x _dl_debug_state
Date: Tue, 11 May 2021 10:00:01 +0200 [thread overview]
Message-ID: <20210511080001.GA11334@oc3748833570.ibm.com> (raw)
In-Reply-To: <22cab26b-8931-ffc0-5324-bff640773924@linaro.org>
On Mon, May 10, 2021 at 11:16:46AM -0300, Luis Machado wrote:
> cc-ing Maciej and Ulrich for feedback about MIPS / rs6000. I see both
> architectures rely on marking some symbols as special, for different
> purposes.
On POWER we use the special symbol marker to identify symbols with
a local entrypoint offset. This is to make sure, when setting a
breakpoint on the symbol, that we can set it at the local entrypoint
instead of the global entrypoint.
For stap probes, this is irrelevant, since there we are directly
told the address where to set the breakpoint. So there should
be no problem for this architecture.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU/Linux compilers and toolchain
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2021-05-11 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b0b35028-2463-dd00-14af-22be2e7b6ff6@linaro.org>
[not found] ` <878s4qb7fj.fsf@oldenburg.str.redhat.com>
[not found] ` <07b03137-a083-dada-68da-965779cd41ff@linaro.org>
[not found] ` <87bl9mi4xi.fsf@paluero>
2021-05-08 10:55 ` Florian Weimer
2021-05-10 14:16 ` Luis Machado
2021-05-11 8:00 ` Ulrich Weigand [this message]
2021-05-24 14:22 ` Luis Machado
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=20210511080001.GA11334@oc3748833570.ibm.com \
--to=uweigand@de.ibm.com \
--cc=doko@debian.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=macro@orcam.me.uk \
--cc=sergiodj@sergiodj.net \
--cc=systemtap@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).