From: Doug Evans <dje@google.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] New board file remote-stdio-gdbserver.exp
Date: Mon, 13 May 2013 21:24:00 -0000 [thread overview]
Message-ID: <CADPb22T13N=jaCPYEsAmdywOmHVr48DH3qvTx9wOY0k6tOJvsA@mail.gmail.com> (raw)
In-Reply-To: <CAEG7qUyS8Uiis5obsvnK3OEQvOHwTXWdxt2gKOLiT9PUH5CFWw@mail.gmail.com>
On Fri, May 10, 2013 at 2:47 PM, Sterling Augustine
<saugustine@google.com> wrote:
> Hello,
>
> Enclosed is a new board file that enables testing using stdio via
> gdbserver on a remote server. This is useful if, for example, firewall
> policies disallow gdbserver from opening a port to listen on.
>
> It follows Doug Evans' native-stdio-gdbserver.exp fairly closely. I
> had originally tried to combine the two, but it got kind of ugly.
>
> It's use is documented at the top of the file.
>
> OK for trunk?
>
> Sterling
>
> 2013-05-10 Sterling Augustine <saugustine@google.com>
>
> * boards/remote-stdio-gdbserver.exp: New file.
Since there is a fair bit of commonality, another way to go is to
begin your file with
load_board_description "native-stdio-gdbserver"
and then add or override the bits you need.
Factoring out bits in native-stdio-gdbserver.exp so that they can be
overridden may be needed.
For proc ${board}_download you could just redefine it in your file
(seems simplest).
I think I'd prefer that if it works for you.
next prev parent reply other threads:[~2013-05-13 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 21:47 Sterling Augustine
2013-05-13 21:24 ` Doug Evans [this message]
2013-05-21 17:50 ` Sterling Augustine
2013-05-21 17:54 ` Doug Evans
2013-05-21 17:59 ` 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='CADPb22T13N=jaCPYEsAmdywOmHVr48DH3qvTx9wOY0k6tOJvsA@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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