public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/30386] Thumb flag on ARMv6 Mach-O ignored, symbols assumed to not be Thumb
Date: Tue, 25 Apr 2023 11:51:53 +0000 [thread overview]
Message-ID: <bug-30386-4717-4iVHr4zcev@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30386-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30386
--- Comment #5 from Luis Machado <luis.machado at arm dot com> ---
Besides the fact the file isn't an ELF file, I don't see any mapping symbols in
the file either.
The thumb discovery code in gdb uses some mechanisms to figure out a particular
address/instruction is thumb. One of them is the presence of the mapping
symbols.
See here:
https://github.com/ARM-software/abi-aa/blob/main/aaelf32/aaelf32.rst#mapping-symbols
The other way is by looking at the address' LSB. If it is 1, then it is thumb,
otherwise it is non-thumb.
During execution, it also fetches the thumb state from the status register.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-04-25 11:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 19:28 [Bug symtab/30386] New: " hikari at noyu dot me
2023-04-24 22:47 ` [Bug symtab/30386] " hikari at noyu dot me
2023-04-25 11:39 ` luis.machado at arm dot com
2023-04-25 11:40 ` [Bug tdep/30386] " luis.machado at arm dot com
2023-04-25 11:45 ` luis.machado at arm dot com
2023-04-25 11:51 ` luis.machado at arm dot com [this message]
2023-04-25 11:52 ` luis.machado at arm dot com
2023-04-25 14:44 ` hikari at noyu dot me
2023-04-25 15:20 ` hikari at noyu dot me
2023-04-25 15:46 ` hikari at noyu dot me
2023-04-25 16:25 ` hikari at noyu dot me
2023-04-26 5:37 ` luis.machado at arm dot com
2023-04-26 5:40 ` luis.machado at arm dot com
2023-04-26 9:27 ` hikari at noyu dot me
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-30386-4717-4iVHr4zcev@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).