From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25622 invoked by alias); 23 Feb 2004 15:37:44 -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 25615 invoked from network); 23 Feb 2004 15:37:42 -0000 Received: from unknown (HELO miranda.se.axis.com) (193.13.178.2) by sources.redhat.com with SMTP; 23 Feb 2004 15:37:42 -0000 Received: from axis.com (ironmaiden.se.axis.com [10.13.8.120]) by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id i1NFb8nI029677; Mon, 23 Feb 2004 16:37:09 +0100 Message-ID: <403A1E24.3090801@axis.com> Date: Mon, 23 Feb 2004 15:37:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 MIME-Version: 1.0 To: Daniel Jacobowitz CC: gdb-patches@sources.redhat.com Subject: Re: Remote target (CRIS) DejaGNU config scripts References: <4034E534.3070606@axis.com> <20040219171932.GA2598@nevyn.them.org> In-Reply-To: <20040219171932.GA2598@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-02/txt/msg00636.txt.bz2 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? -- Orjan Friberg Axis Communications