From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26198 invoked by alias); 23 Feb 2004 15:39:28 -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 26191 invoked from network); 23 Feb 2004 15:39:28 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 23 Feb 2004 15:39:28 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AvIB4-00089J-T9; Mon, 23 Feb 2004 10:39:26 -0500 Date: Mon, 23 Feb 2004 15:39:00 -0000 From: Daniel Jacobowitz To: Orjan Friberg Cc: gdb-patches@sources.redhat.com Subject: Re: Remote target (CRIS) DejaGNU config scripts Message-ID: <20040223153926.GA31279@nevyn.them.org> Mail-Followup-To: Orjan Friberg , gdb-patches@sources.redhat.com References: <4034E534.3070606@axis.com> <20040219171932.GA2598@nevyn.them.org> <403A1E24.3090801@axis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <403A1E24.3090801@axis.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-02/txt/msg00637.txt.bz2 On Mon, Feb 23, 2004 at 04:37:08PM +0100, Orjan Friberg wrote: > Daniel Jacobowitz wrote: > > > >I've attached a modified version that I'm using as I type. It works > >pretty much OK. You may need to change host_exec to server_exec in the > >call to gdbserver_gdb_load in config/gdbserver.exp, depending on your > >setup. > > Thanks Daniel, I think I'm halfway there. One thing has me puzzled > though, hostname vs. sockethost (from your example): > > >set_board_info hostname innovator > >set_board_info sockethost "innovator:" > > Substituting innovator with my board's IP address (10.13.8.125) this > results in: > > On the board: gdbserver 10.13.8.125:2346 > On the host: target remote 10.13.8.125:2346 > > But the gdbserver should be started with the host's IP address as an > argument, not the IP address of the board itself, right? (Changing the > sockethost variable to the host's IP address only results in the reverse > situation, which means "target remote" will try and listen to a local > port.) Or am I totally missing something? All you're missing is that gdbserver ignores the IP specified - it just wants there to be a colon. When I do it by hand I say ":5555". Theoretically, gdbserver should parse the IP, and make sure only to accept a connection from that IP... but it doesn't. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer