public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] sim: ppc: track closed state of file descriptors 0, 1, and 2.
Date: Wed, 30 Dec 2015 00:30:00 -0000	[thread overview]
Message-ID: <90d99f327063af7d87c61234896d4a1dbe073a43@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 90d99f327063af7d87c61234896d4a1dbe073a43 ***

Author: Kevin Buettner <kevinb@redhat.com>
Branch: master
Commit: 90d99f327063af7d87c61234896d4a1dbe073a43

sim: ppc: track closed state of file descriptors 0, 1, and 2.

This change tracks the "closed" state of file descriptors 0, 1, and 2,
introducing the function fdbad() to emul_netbsd.c and emul_unix.c.
Note that a function of the same name and purpose exists in
sim/common/callback.c.

This patch eliminates all of the "unresolved testcases" when testing
GDB against the powerpc simulator.

This occurs because the powerpc simulator closes, on behalf of the
testcase, the file descriptors associated with stdin, stdout, and
stderr.  GDB still needs these descriptors to communicate with the
user or, in this case, with the testing framework.


             reply	other threads:[~2015-12-30  0:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30  0:30 sergiodj+buildbot [this message]
2015-12-30  0:30 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2015-12-30  0:41 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2015-12-30  0:42 ` Failures on Debian-i686, " sergiodj+buildbot
2015-12-30  0:47 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-12-30  0:49 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-30  0:49 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2015-12-30  0:55 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-30  1:07 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2015-12-30  1:19 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-30  1:26 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2015-12-30  1:27 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2015-12-30  1:36 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-12-30  1:39 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot
2015-12-30  1:42 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-12-30  1:57 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2015-12-30  8:41 ` Failures on Debian-x86_64-native-gdbserver-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=90d99f327063af7d87c61234896d4a1dbe073a43@gdb-build \
    --to=sergiodj+buildbot@redhat.com \
    --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).