This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: problem with fetch_link_map_offsets
- From: Kevin Buettner <kevinb at redhat dot com>
- To: "Kris Warkentin" <kewarken at qnx dot com>, "Kevin Buettner" <kevinb at redhat dot com>, "Gdb at Sources dot Redhat dot Com" <gdb at sources dot redhat dot com>
- Date: Mon, 9 Jun 2003 14:34:28 -0700
- Subject: Re: problem with fetch_link_map_offsets
- References: <020701c30dc3$bd8cf020$0202040a@catdog> <1030429150643.ZM6454@localhost.localdomain> <030401c30e63$9c270560$0202040a@catdog> <1030429162815.ZM6720@localhost.localdomain> <00e501c30e94$e285e400$0202040a@catdog> <033401c32ecd$07d8adc0$0202040a@catdog>
On Jun 9, 5:19pm, Kris Warkentin wrote:
> Say, for example, I go into arm-tdep.c and comment out the section that
> registers a gdbarch osabi sniffer. Now my arm port works fine: it uses
> GDB_OSABI_QNXNTO and everything is hunky-dory. So the problem is that the
> sniffer says, "Oh, it's GDB_OSABI_ARM_APCS, let's set that up." and then all
> of my init stuff is out the door.
>
> The question is, how do I deal with this? There is nothing to distinguish a
> Neutrino binary from any other elf file. I tried registering another
> sniffer that just returned GDB_OSABI_QNXNTO but then it squawked that it got
> two osabi results. I'm assuming that this is probably what I'm running into
> on all my targets.
It sounds to me like the problem is with the sniffer(s). If the sniffer
is determining GDB_OSABI_ARM_APCS for a QNX binary, that's bad and the
sniffer ought to be fixed.
Kevin