From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7242 invoked by alias); 6 Feb 2003 15:13:51 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7233 invoked from network); 6 Feb 2003 15:13:50 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 6 Feb 2003 15:13:50 -0000 Received: from smtp.ott.qnx.com (smtp.ott.qnx.com [10.0.2.158]) by hub.ott.qnx.com (8.9.3/8.9.3) with ESMTP id KAA29990; Thu, 6 Feb 2003 10:03:20 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id KAA29634; Thu, 6 Feb 2003 10:13:49 -0500 Message-ID: <1e9301c2cdf2$484c60e0$0202040a@catdog> From: "Kris Warkentin" To: "Mark Kettenis" Cc: References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <86d6m6e9p7.fsf@elgar.kettenis.dyndns.org> <1dfb01c2cd5c$b2cf98b0$0202040a@catdog> <1e0d01c2cd5f$7d69d430$0202040a@catdog> <200302052224.h15MO2rl001579@elgar.kettenis.dyndns.org> Subject: Re: patch to add QNX NTO i386 support Date: Thu, 06 Feb 2003 15:13:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-SW-Source: 2003-02/txt/msg00215.txt.bz2 > > > You'll also need to find a way to distinguish QNX binaries from other > > > OS'es. The hardware breakpoint stuff will have to be moved to the > > > nm.h. Most of the other stuff shouldn't be necessary or should be > > > moved there too. > > > > Okay. Not sure how but I'll look into it. Once I've done that, do I > > register an osabi_sniffer to determine the binary? > > I don't think this is going to work. Our binaries are very generic elf with > no special sections or anything to distinguish them. > > In that case you'll have to provide a default OS/ABI for your target. > Add something like: > > *-*-nto*) gdb_osabi=GDB_OSABI_QNX ;; > > to the appropriate case-statement at the end of configure.tgt. This seems like a good way to do it. I added GDB_OSABI_QNXNTO to defs.h. I'm in general using 'nto' since that describes the kernel but people don't always know that so I made sure to leave the 'qnx' in a few places like here and config/tm-qnxnto.h. > The only way to tell that we're targetting a qnx binary will be when > someone types 'target qnx ...'. Is it acceptable to have the > gdbarch stuff come into play when someone does that targetting? > > I'm not sure. If the "qnx" protocol implies that the OS/ABI is QNX, > this would make sense to me, but there are other people on this list > that could judge better. You're right about this. It's unlikely that anyone else would use our qnx pdebug protocol for remote debugging but one of my future projects is to port the gdbserver to Neutrino. People wouldn't necessarily need to use pdebug but in this case, there would really be no way of knowing the ABI other than having a default set. cheers, Kris