Browse Source

* common/filestuff.c (gdb_fopen_cloexec): Do not try to use "e"

mode if operating system doesn't know O_CLOEXEC.
binutils-2_24-branch
Pierre Muller 13 years ago
parent
commit
88505fac1c
  1. 7
      gdb/ChangeLog
  2. 8
      gdb/common/filestuff.c

7
gdb/ChangeLog

@ -1,3 +1,10 @@
2013-09-14 Pierre Muller <muller@sourceware.org>
Tom Tromey <tromey@redhat.com>
Pedro Alves <palves@redhat.com>
* common/filestuff.c (gdb_fopen_cloexec): Do not try to use "e"
mode if operating system doesn't know O_CLOEXEC.
2013-09-13 Jan Kratochvil <jan.kratochvil@redhat.com>
Code cleanup.

8
gdb/common/filestuff.c

@ -311,7 +311,13 @@ FILE *
gdb_fopen_cloexec (const char *filename, const char *opentype)
{
FILE *result = NULL;
static int fopen_e_ever_failed;
/* Probe for "e" support once. But, if we can tell the operating
system doesn't know about close on exec mode "e" without probing,
skip it. E.g., the Windows runtime issues an "Invalid parameter
passed to C runtime function" OutputDebugString warning for
unknown modes. Assume that if O_CLOEXEC is zero, then "e" isn't
supported. */
static int fopen_e_ever_failed = O_CLOEXEC == 0;
if (!fopen_e_ever_failed)
{

Loading…
Cancel
Save