public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] remote-stdio-gdbserver: Pass "target" to remote_exec to delete file
Date: Thu, 08 Mar 2018 23:24:00 -0000	[thread overview]
Message-ID: <4872dc464db25a003c66ef91773b616495cc504f@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 4872dc464db25a003c66ef91773b616495cc504f ***

Author: Simon Marchi <simon.marchi@ericsson.com>
Branch: master
Commit: 4872dc464db25a003c66ef91773b616495cc504f

remote-stdio-gdbserver: Pass "target" to remote_exec to delete file

As described here

  https://sourceware.org/bugzilla/show_bug.cgi?id=22841

there seems to be situations where the remote-stdio-gdbserver board
fails to delete the uploaded binary file.  Passing "target" fixes the
issue for Christian who reported the bug.

I did not experience this problem, but passing "target" to remote_exec
still works for me, so I'm fine with changing it.

Any objection?

gdb/testsuite/ChangeLog:

	PR gdb/22841
	* boards/remote-stdio-gdbserver.exp (${board}_file): Pass
	"target" to remote_exec.


             reply	other threads:[~2018-03-08 23:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 23:24 sergiodj+buildbot [this message]
2018-03-08 23:24 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-03-08 23:55 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-03-09  0:10 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-09  0:12 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-09  0:14 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-03-09  0:33 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-09  0:35 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-09  0:37 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-03-09  0:38 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-03-09  0:48 ` Failures on Fedora-x86_64-m32, branch master sergiodj+buildbot
2018-03-09  1:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-09  1:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-09 13:57 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-09 15:01 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot

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=4872dc464db25a003c66ef91773b616495cc504f@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).