Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: Daniel Jacobowitz <drow@false.org>,
	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:30:00 -0000	[thread overview]
Message-ID: <46C988F7.1030102@de.ibm.com> (raw)
In-Reply-To: <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


  reply	other threads:[~2007-08-20 12:30 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 [this message]
2007-08-20 12:47     ` Daniel Jacobowitz

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=46C988F7.1030102@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=drow@false.org \
    --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