This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] New board file remote-stdio-gdbserver.exp
- From: Doug Evans <dje at google dot com>
- To: Sterling Augustine <saugustine at google dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Mon, 13 May 2013 14:24:00 -0700
- Subject: Re: [PATCH] New board file remote-stdio-gdbserver.exp
- References: <CAEG7qUyS8Uiis5obsvnK3OEQvOHwTXWdxt2gKOLiT9PUH5CFWw at mail dot gmail dot 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.