From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20703 invoked by alias); 6 Feb 2003 18:19:32 -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 20695 invoked from network); 6 Feb 2003 18:19:31 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 6 Feb 2003 18:19:31 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 4310F3CC9; Thu, 6 Feb 2003 13:19:29 -0500 (EST) Message-ID: <3E42A731.1060306@redhat.com> Date: Thu, 06 Feb 2003 18:19:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.1) Gecko/20021211 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Warkentin Cc: Mark Kettenis , gdb-patches@sources.redhat.com Subject: Re: patch to add QNX NTO i386 support 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> <1e9301c2cdf2$484c60e0$0202040a@catdog> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00218.txt.bz2 >> 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. FYI, A long term objective of GDB is to get the sequence: $ gdb (gdb) target remote who-knows-what-we-debugging:47 Connected to target who-knows-what-we-debugging. Architecture set to now-we-know. (gdb) info registers ... display of now-we-know architecture's registers ... (gdb) This involves the target supplying the thread's architecture via the target stack .... Andrew