From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21365 invoked by alias); 5 Feb 2003 21:43:03 -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 21358 invoked from network); 5 Feb 2003 21:43:03 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 5 Feb 2003 21:43:03 -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 QAA06412; Wed, 5 Feb 2003 16:32:36 -0500 Received: from catdog ([10.4.2.2]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id QAA11024; Wed, 5 Feb 2003 16:43:02 -0500 Message-ID: <1e0d01c2cd5f$7d69d430$0202040a@catdog> From: "Kris Warkentin" To: "Kris Warkentin" , "Mark Kettenis" Cc: References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <86d6m6e9p7.fsf@elgar.kettenis.dyndns.org> <1dfb01c2cd5c$b2cf98b0$0202040a@catdog> Subject: Re: patch to add QNX NTO i386 support Date: Wed, 05 Feb 2003 21:43: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/msg00199.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. 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? cheers, Kris