This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Remote target (CRIS) DejaGNU config scripts
- From: Orjan Friberg <orjan dot friberg at axis dot com>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 23 Feb 2004 16:37:08 +0100
- Subject: Re: Remote target (CRIS) DejaGNU config scripts
- Organization: Axis Communications
- References: <4034E534.3070606@axis.com> <20040219171932.GA2598@nevyn.them.org>
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 <file>
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