public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Luis Machado via Gdb <gdb@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>,
	 Luis Machado via Libc-alpha <libc-alpha@sourceware.org>,
	 Luis Machado <luis.machado@linaro.org>,
	doko@debian.org
Subject: Re: GDB shared library tracking with stap probes x _dl_debug_state
Date: Fri, 07 May 2021 17:56:25 -0400	[thread overview]
Message-ID: <87bl9mi4xi.fsf@paluero> (raw)
In-Reply-To: <07b03137-a083-dada-68da-965779cd41ff@linaro.org> (Luis Machado via Gdb's message of "Fri, 7 May 2021 18:44:47 -0300")

On Friday, May 07 2021, Luis Machado via Gdb wrote:

> On 5/7/21 5:44 PM, Florian Weimer wrote:
>> * Luis Machado via Libc-alpha:
>> 
>>> That's all fine, but there is one small detail that doesn't work for
>>> armhf, and that is discovering if we're dealing with a PC that is arm
>>> mode or thumb mode.
>> Is it possible to recognize Arm mode vs thumb mode based on the NOP
>> encoding at the probe address?
>> 
>
> If we know the instruction is a NOP, it might be possible.

I think it's guaranteed that the instruction is always going to be a
NOP.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

  reply	other threads:[~2021-05-07 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 19:42 Luis Machado
2021-05-07 20:44 ` Florian Weimer
2021-05-07 21:44   ` Luis Machado
2021-05-07 21:56     ` Sergio Durigan Junior [this message]
2021-05-08 10:55       ` Florian Weimer
2021-05-10 14:16         ` Luis Machado
2021-05-11  8:00           ` Ulrich Weigand
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=87bl9mi4xi.fsf@paluero \
    --to=sergiodj@sergiodj.net \
    --cc=doko@debian.org \
    --cc=fweimer@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=luis.machado@linaro.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).