From: Pedro Alves <palves@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>
Subject: Re: [PATCH] Implement ${board}_{exec,spawn} for native-extended-gdbserver
Date: Wed, 04 Feb 2015 13:06:00 -0000 [thread overview]
Message-ID: <54D21931.8040806@redhat.com> (raw)
In-Reply-To: <1423005658-31405-1-git-send-email-sergiodj@redhat.com>
On 02/04/2015 12:20 AM, Sergio Durigan Junior wrote:
> diff --git a/gdb/testsuite/boards/native-extended-gdbserver.exp b/gdb/testsuite/boards/native-extended-gdbserver.exp
> index 57503db..0059c4e 100644
> --- a/gdb/testsuite/boards/native-extended-gdbserver.exp
> +++ b/gdb/testsuite/boards/native-extended-gdbserver.exp
> @@ -23,12 +23,6 @@
> load_generic_config "extended-gdbserver"
> load_board_description "gdbserver-base"
>
> -# By default, dejagnu makes the board remote unless the board name
> -# matches localhost. Force it to be NOT remote.
> -global board
> -global board_info
> -set board_info($board,isremote) 0
I don't think we can/should remove this. That'll make
"is_remote" checks all over the testsuite return true,
and thus skip tests that weren't skipped before. E.g.,
solib-display.exp.
I think we need to instead do here what ${board}_spawn
is already doing. That is, remove any target variant
specifications from $board, like:
--- a/gdb/testsuite/boards/native-extended-gdbserver.exp
+++ b/gdb/testsuite/boards/native-extended-gdbserver.exp
@@ -27,7 +27,9 @@ load_board_description "gdbserver-base"
# matches localhost. Force it to be NOT remote.
global board
global board_info
-set board_info($board,isremote) 0
+# Remove any target variant specifications from the name.
+set baseboard [lindex [split $board "/"] 0]
+set board_info($baseboard,isremote) 0
I'm testing that.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-04 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 23:21 Sergio Durigan Junior
2015-02-04 13:06 ` Pedro Alves [this message]
2015-02-04 13:59 ` Pedro Alves
2015-02-06 8:45 ` Doug Evans
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=54D21931.8040806@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.org \
--cc=sergiodj@redhat.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