From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5895 invoked by alias); 20 Feb 2003 00:42:53 -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 5879 invoked from network); 20 Feb 2003 00:42:52 -0000 Received: from unknown (HELO localhost.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 20 Feb 2003 00:42:52 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 44ED42ED1; Wed, 19 Feb 2003 19:47:37 -0500 (EST) Message-ID: <3E5425A9.2010609@redhat.com> Date: Thu, 20 Feb 2003 00:42:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD i386; en-US; rv:1.0.2) Gecko/20030217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Warkentin Cc: Daniel Jacobowitz , gdb-patches@sources.redhat.com Subject: Re: patch to add QNX NTO i386 support References: <01dd01c2d3aa$d4c1b1c0$0202040a@catdog> <20030213220751.GA15234@nevyn.them.org> <020c01c2d3ae$c7cb39b0$0202040a@catdog> <20030213222922.GA15783@nevyn.them.org> <000901c2d3ba$cb19aaf0$2a00a8c0@dash> <20030214000311.GA18154@nevyn.them.org> <003d01c2d3bd$b136bf30$2a00a8c0@dash> <20030214001316.GA18590@nevyn.them.org> <017c01c2d3c1$6196b210$2a00a8c0@dash> <3E4EBCF0.8070003@redhat.com> <20030217154403.GA16683@nevyn.them.org> <3E5111C7.5080708@redhat.com> <064301c2d6b6$0c381870$0202040a@catdog> <3E52A642.2010403@redhat.com> <000901c2d79d$c32c8fb0$2a00a8c0@dash> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00460.txt.bz2 > Alright. Perhaps the 'exec-file' command? It seems to me that > 'symbol-file' and 'exec-file' should combine into the 'file' command. The > problem is that 'exec-file /tmp/some_file' fails if there is no > /tmp/some_file. Maybe we could make the exec-file command unconditional? > That way the target_ops run command can deal with it. If this is strictly a remote target setting that only applies to the remote side, why not `set remote ....'. Andrew