From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29652 invoked by alias); 14 Feb 2003 00:03:19 -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 29644 invoked from network); 14 Feb 2003 00:03:19 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 14 Feb 2003 00:03:19 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18jVD4-0007Nv-00; Thu, 13 Feb 2003 20:04:14 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18jTJv-0004k4-00; Thu, 13 Feb 2003 19:03:11 -0500 Date: Fri, 14 Feb 2003 00:03:00 -0000 From: Daniel Jacobowitz To: Kris Warkentin Cc: Mark Kettenis , Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: patch to add QNX NTO i386 support Message-ID: <20030214000311.GA18154@nevyn.them.org> Mail-Followup-To: Kris Warkentin , Mark Kettenis , Andrew Cagney , gdb-patches@sources.redhat.com 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> <000901c2d3ba$cb19aaf0$2a00a8c0@dash> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000901c2d3ba$cb19aaf0$2a00a8c0@dash> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00322.txt.bz2 On Thu, Feb 13, 2003 at 06:51:13PM -0500, Kris Warkentin wrote: > > > > 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. These are all things I'd want gdbserver to do, at some point. Need to do it with extensions to the existing remote protocol (or kick the bucket and create a new one). That said, I still think you should be using "file" above. File specifies the main program, and that's what it is. Then you can give whatever path you want to the stub. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer