[pushed] Remove is_remote target check from gdb.base/dprintf-non-stop.exp
Commit Message
From: Simon Marchi <simon.marchi@polymtl.ca>
1. is_remote is not the right check.
2. Both Simon & Pedro ran it continuously for some time against
native-gdbserver and didn't see a failure.
3. The test has been running against native-extended-gdbserver anyway.
gdb/testsuite/ChangeLog:
2017-10-12 Simon Marchi <simon.marchi@polymtl.ca>
Pedro Alves <palves@redhat.com>
* gdb.base/dprintf-non-stop.exp: Remove is_remote target check.
---
gdb/testsuite/ChangeLog | 5 +++++
gdb/testsuite/gdb.base/dprintf-non-stop.exp | 6 ------
2 files changed, 5 insertions(+), 6 deletions(-)
@@ -1,3 +1,8 @@
+2017-10-12 Simon Marchi <simon.marchi@polymtl.ca>
+ Pedro Alves <palves@redhat.com>
+
+ * gdb.base/dprintf-non-stop.exp: Remove is_remote target check.
+
2017-10-12 Pedro Alves <palves@redhat.com>
Simon Marchi <simon.marchi@polymtl.ca>
@@ -13,12 +13,6 @@
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
-if [is_remote target] then {
- # Testing with remote/non-stop is racy at the moment.
- unsupported "testing dprintf with remote/non-stop is not supported."
- return 0
-}
-
standard_testfile
set executable ${testfile}