From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7969 invoked by alias); 9 Jun 2003 21:34:34 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 7949 invoked from network); 9 Jun 2003 21:34:34 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 9 Jun 2003 21:34:34 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h59LYYH16363 for ; Mon, 9 Jun 2003 17:34:34 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h59LYYI22438; Mon, 9 Jun 2003 17:34:34 -0400 Received: from localhost.localdomain (vpn50-20.rdu.redhat.com [172.16.50.20]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h59LYXv12841; Mon, 9 Jun 2003 17:34:33 -0400 Received: (from kev@localhost) by localhost.localdomain (8.11.6/8.11.6) id h59LYSp18479; Mon, 9 Jun 2003 14:34:28 -0700 Date: Mon, 09 Jun 2003 21:34:00 -0000 From: Kevin Buettner Message-Id: <1030609213428.ZM18478@localhost.localdomain> In-Reply-To: "Kris Warkentin" "Re: problem with fetch_link_map_offsets" (Jun 9, 5:19pm) 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> To: "Kris Warkentin" , "Kevin Buettner" , "Gdb@Sources.Redhat.Com" Subject: Re: problem with fetch_link_map_offsets MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-06/txt/msg00122.txt.bz2 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