This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [Patch]: Fix sockethost handling in board config
- From: Markus Deuling <deuling at de dot ibm dot com>
- To: Daniel Jacobowitz <drow at false dot org>, Ulrich Weigand <uweigand at de dot ibm dot com>, GDB Patches <gdb-patches at sourceware dot org>
- Date: Mon, 20 Aug 2007 14:28:39 +0200
- Subject: Re: [Patch]: Fix sockethost handling in board config
- References: <46C92424.2040503@de.ibm.com> <20070820113153.GB5195@caradoc.them.org>
Daniel Jacobowitz schrieb:
this patch fixes handling of gdbserver parameter in
testsuite/lib/gdbserver-support.exp.
When using the testsuite remotely there are two parameters possible for remote
host configuration:
sockethost and socketport. Currently sockethost is ignored.
Why does it need to be fixed? gdbserver doesn't do anything with the
hostname, so there's no need to pass it, and the existing sockethost
variable is honored. That's "sockethost", not "gdb,sockethost".
Neither "sockethost" nor "gdb,sockethost" is honored currently.
<snip>
# Export the host:port pair.
set gdbport $debughost$portnum
# Fire off the debug agent. This flavour of gdbserver takes as
# arguments the port information, the name of the executable file to
# be debugged, and any arguments.
set gdbserver_command "$gdbserver :$portnum $gdbserver_server_exe
</snip>
The hostname isnt passed to the gdbserver command.
Why is it gdb,socketport and sockethost?!? I think it makes sense to name the two
variables in the same way. They are a pair that belongs together.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com