From: Kris Warkentin <kewarken@qnx.com>
To: gdb@sources.redhat.com
Subject: Question for ARM experts
Date: Wed, 30 Jun 2004 20:40:00 -0000 [thread overview]
Message-ID: <40E30C91.1030503@qnx.com> (raw)
In arm-tdep.c I see that if we get GDB_OSABI_UNKNOWN we assume
GDB_OSABI_ARM_APCS. What would the consequences of not doing that be
for other arm targets?
The problem is, there isn't anything particularily distinct about QNX
Neutrino binaries so I've got a generic Neutrino sniffer that basically
says, "Am I connected to a Neutrino target? Okay, then let's use the
Neutrino ABI stuff." Arm is the only one that falls apart for this
because when I return GDB_OSABI_QNXNTO and arm_elf_osabi_sniffer() in
arm-tdep.c returns APCS, gdbarch_lookup_osabi() goes, "Argh!! Two
OSABIs...*choke*"
So here's the thing: if I allow arm_elf_osabi_sniffer to return
GDB_OSABI_UNKNOWN in the case of ELFOSABI_ARM, my sniffer works fine.
The question is, if we allow the APCS fallback in the case of
ELFOSABI_UNKNOWN but not in ELFOSABI_ARM, is that going to break the world?
If so, does anyone have any suggestions for how to deal with this?
cheers,
Kris
reply other threads:[~2004-06-30 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40E30C91.1030503@qnx.com \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).