Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sterling Augustine <saugustine@google.com>
To: gdb-patches <gdb-patches@sourceware.org>
Cc: Doug Evans <dje@google.com>
Subject: [patch] Set remote port numbers correctly in remote-stdio-gdbserver.exp
Date: Thu, 29 Aug 2013 18:40:00 -0000	[thread overview]
Message-ID: <CAEG7qUy506wJtiaYncj7cAJtOAjDQWQBf-H5rLeZFHJi3xbLpw@mail.gmail.com> (raw)

The enclosed fairly straightforward patch to the board file
remote-stdio-gdbserver.exp fixes the syntax scp and rsh use to select
the remote port, which was broken before.

Tested with both default and custom remote ports.

OK for trunk?

Sterling

testsuite/ChangeLog

2013-08-29  Sterling Augustine  <saugustine@google.com>

        * boards/remote-stdio-gdbserver.exp: Set rcp_prog and
        rsh_prog in new conditional.  Move use of REMOTE_PORTNUM into
        said conditional.


             reply	other threads:[~2013-08-29 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 18:40 Sterling Augustine [this message]
2013-08-29 19:03 ` Sterling Augustine
2013-08-29 19:10   ` Doug Evans
2013-08-29 19:22     ` Sterling Augustine

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=CAEG7qUy506wJtiaYncj7cAJtOAjDQWQBf-H5rLeZFHJi3xbLpw@mail.gmail.com \
    --to=saugustine@google.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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