From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: "Invalid parameter passed to C runtime function" from MinGW GDB
Date: Mon, 19 Nov 2018 22:06:00 -0000 [thread overview]
Message-ID: <874lccpvra.fsf@tromey.com> (raw)
In-Reply-To: <838t1qtjty.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 18 Nov 2018 18:46:17 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> I propose to fix this as below. Any objections to committing this to
Eli> master (with a suitable ChangeLog, of course)?
Eli> diff --git a/gdb/common/filestuff.c b/gdb/common/filestuff.c
Eli> index d4bd1a8..3fa035a 100644
Eli> --- a/gdb/common/filestuff.c
Eli> +++ b/gdb/common/filestuff.c
Eli> @@ -300,8 +300,10 @@ gdb_fopen_cloexec (const char *filename, const char *opentype)
Eli> skip it. E.g., the Windows runtime issues an "Invalid parameter
Eli> passed to C runtime function" OutputDebugString warning for
Eli> unknown modes. Assume that if O_CLOEXEC is zero, then "e" isn't
Eli> - supported. */
Eli> - static int fopen_e_ever_failed_einval = O_CLOEXEC == 0;
Eli> + supported. On MinGW, O_CLOEXEC is an alias of O_NOINHERIT, and
Eli> + "e" isn't supported. */
Eli> + static int fopen_e_ever_failed_einval =
Eli> + O_CLOEXEC == 0 || O_CLOEXEC == O_NOINHERIT;
Looks reasonable to me, thanks.
Tom
next prev parent reply other threads:[~2018-11-19 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 16:46 Eli Zaretskii
2018-11-19 22:06 ` Tom Tromey [this message]
2018-11-20 16:52 ` Eli Zaretskii
2018-11-20 16:54 ` 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=874lccpvra.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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