From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19716 invoked by alias); 13 Feb 2003 23:48:46 -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 19709 invoked from network); 13 Feb 2003 23:48:46 -0000 Received: from unknown (HELO hub.ott.qnx.com) (209.226.137.76) by 172.16.49.205 with SMTP; 13 Feb 2003 23:48:46 -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 SAA17298; Thu, 13 Feb 2003 18:37:37 -0500 Received: from dash ([192.168.20.26]) by smtp.ott.qnx.com (8.8.8/8.6.12) with SMTP id SAA06941; Thu, 13 Feb 2003 18:48:44 -0500 Message-ID: <000901c2d3ba$cb19aaf0$2a00a8c0@dash> From: "Kris Warkentin" To: "Daniel Jacobowitz" Cc: "Mark Kettenis" , "Andrew Cagney" , References: <1c3601c2cbc1$72eac3b0$0202040a@catdog> <3E40387D.50001@redhat.com> <008f01c2ce4b$427295f0$2a00a8c0@dash> <86lm0r3nha.fsf@elgar.kettenis.dyndns.org> <01dd01c2d3aa$d4c1b1c0$0202040a@catdog> <20030213220751.GA15234@nevyn.them.org> <020c01c2d3ae$c7cb39b0$0202040a@catdog> <20030213222922.GA15783@nevyn.them.org> Subject: Re: patch to add QNX NTO i386 support Date: Thu, 13 Feb 2003 23:48: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/msg00319.txt.bz2 > > > Silly question - why not say "file blah" here? That'll set exec_bfd, > > > and you'll be just fine. > > > > > > Not silly. If you say 'file' you have tied yourself to the host and target > > file being the same. I need to be able to get syms from /home/kewarken/foo > > and run /tmp/foo. > > Wait, but from your earlier sequence, isn't /home/kewarken/foo on the > host and uploaded to /tmp/foo on the target? > > I don't follow why GDB needs to know anything about the target > filename. I can see that this remote protocol is very different from > the normal one, if you're ssending full paths. Yeah. The remote system is an Unix OS with filesystem, etc. just like the host. I suppose an interesting thing to do might be to have the remote server remember what was uploaded but that would actually limit you. We can upload shared objects, set remote LD_LIBRARY_PATH, etc. or not upload at all but just run an arbitrary binary on the remote (which could be nfs or samba mounted) or even attach to a running pid on the remote. Flexible. cheers, Kris