Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tromey@redhat.com>,
	ktietz@redhat.com,        gdb-patches@sourceware.org
Subject: Re: [patch] Minor O_CLOEXEC optimization, "regression" fix
Date: Wed, 09 Oct 2013 17:41:00 -0000	[thread overview]
Message-ID: <20131009174124.GA20135@host2.jankratochvil.net> (raw)
In-Reply-To: <83bo2yqrop.fsf@gnu.org>

On Wed, 09 Oct 2013 19:28:54 +0200, Eli Zaretskii wrote:
> This patch confused me: it tests whether O_CLOEXEC is zero, which it
> is on Windows, so there should be no need to try "e" at all.

If O_CLOEXEC is 0 then the "e" flag is not tried at all, therefore it could
not crash on MS-Windows.


> Therefore, I don't understand why this is still an issue.  What am I
> missing?

On platforms where O_CLOEXEC is 0 this new patch has no effect.


Jan


  reply	other threads:[~2013-10-09 17:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 18:32 Jan Kratochvil
2013-10-08 19:44 ` Tom Tromey
2013-10-09 13:10   ` Jan Kratochvil
2013-10-09 13:34     ` Kai Tietz
2013-10-09 14:41       ` [patchv2] " Jan Kratochvil
2013-10-09 15:48         ` Tom Tromey
2013-10-09 16:01           ` [commit] " Jan Kratochvil
2013-10-09 17:07       ` [patch] " Eli Zaretskii
2013-10-09 17:02     ` Eli Zaretskii
2013-10-09 17:08       ` Tom Tromey
2013-10-09 17:29         ` Eli Zaretskii
2013-10-09 17:41           ` Jan Kratochvil [this message]
2013-10-09 17:58             ` Eli Zaretskii
2013-10-09 18:37               ` Jan Kratochvil
2013-10-09 19:08                 ` Eli Zaretskii

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=20131009174124.GA20135@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ktietz@redhat.com \
    --cc=tromey@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