From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [Patch]: Fix sockethost handling in board config
Date: Mon, 20 Aug 2007 12:47:00 -0000 [thread overview]
Message-ID: <20070820124735.GA9058@caradoc.them.org> (raw)
In-Reply-To: <46C988F7.1030102@de.ibm.com>
On Mon, Aug 20, 2007 at 02:28:39PM +0200, Markus Deuling wrote:
> 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.
That is incorrect.
if [target_info exists sockethost] {
set debughost [target_info sockethost]
} else {
set debughost "localhost:"
}
The sockethost is passed to gdb.
> The hostname isnt passed to the gdbserver command.
Gdbserver doesn't use the hostname, so why should it be passed?
> 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.
True. However, there is an existing and working name. If you change
the name, you're going to break any other working board
configurations.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-08-20 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 5:20 Markus Deuling
2007-08-20 11:32 ` Daniel Jacobowitz
2007-08-20 12:30 ` Markus Deuling
2007-08-20 12:47 ` Daniel Jacobowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070820124735.GA9058@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox