public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18208] Fails in gdb.base/coredump-filter.exp in remote testing
Date: Wed, 08 Apr 2015 16:14:00 -0000	[thread overview]
Message-ID: <bug-18208-4717-iD3zfZPLAp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18208-4717@http.sourceware.org/bugzilla/>

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

--- Comment #10 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
(In reply to Pedro Alves from comment #8)
> BTW, we have other similar uses of sh -c in the tree:

My first attempt was to do:

  remote_exec target "echo 0x123 > /file"

But that failed.  So, I searched in the tree and found those examples that
Pedro mentioned.  Therefore, if the coredump_filter.exp test is failing, I
wouldn't be surprised if those other tests are failing as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-04-08 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 12:44 [Bug gdb/18208] New: " qiyao at gcc dot gnu.org
2015-04-07 12:53 ` [Bug gdb/18208] " qiyao at gcc dot gnu.org
2015-04-07 15:55 ` palves at redhat dot com
2015-04-07 19:23 ` sergiodj at redhat dot com
2015-04-07 19:40 ` sergiodj at redhat dot com
2015-04-08 12:00 ` qiyao at gcc dot gnu.org
2015-04-08 14:57 ` palves at redhat dot com
2015-04-08 15:06 ` palves at redhat dot com
2015-04-08 16:06 ` palves at redhat dot com
2015-04-08 16:13 ` qiyao at gcc dot gnu.org
2015-04-08 16:14 ` sergiodj at redhat dot com [this message]
2015-04-24 10:03 ` cvs-commit at gcc dot gnu.org
2015-04-24 10:09 ` qiyao at gcc dot gnu.org
2015-05-08 11:39 ` cvs-commit at gcc dot gnu.org
2015-05-08 11:58 ` qiyao at gcc dot gnu.org

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=bug-18208-4717-iD3zfZPLAp@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).