From: Mike Frysinger <vapier@gentoo.org>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] PPC sim: Don't close file descriptors 0, 1, or 2
Date: Mon, 16 Nov 2015 23:53:00 -0000 [thread overview]
Message-ID: <20151116235317.GF31395@vapier.lan> (raw)
In-Reply-To: <20151116145807.4aedd84f@pinnacle.lan>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
On 16 Nov 2015 14:58, Kevin Buettner wrote:
> 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.
special casing this logic in the sim looks wrong to me. why
is the testcase itself trying to close stdin/stdout/stderr ?
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-16 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 21:58 Kevin Buettner
2015-11-16 23:53 ` Mike Frysinger [this message]
2015-11-17 4:05 ` Kevin Buettner
2015-11-17 5:41 ` Mike Frysinger
2015-11-17 20:32 ` Kevin Buettner
2015-11-17 21:05 ` Mike Frysinger
2015-12-07 20:29 ` Kevin Buettner
2015-12-30 0:18 ` Mike Frysinger
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=20151116235317.GF31395@vapier.lan \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).