From: "Peter Mularski" <pmularski@clariion.com>
To: "GNU-Win32 (E-mail)" <gnu-win32@cygnus.com>
Subject: Problem: Exec seems to close all file handles
Date: Wed, 22 Jul 1998 16:50:00 -0000 [thread overview]
Message-ID: <000801bdb5ad$9192ab40$732ddd80@cpc45115.us.dg.com> (raw)
Hello,
I have been working with the execv() call in a cygwin32 application, and
have discovered that, when executing a non-cygwin32 app, apparently all the
IO channels are closed when the application is initialized. This is my
guess, but let me explain what I am trying to do. Incidentally, this problem
does not seem to occur in programs that have been compiled with the cygwin32
stuff (gcc, etc). Basically, I have used dup2 to copy some file handles to
sockets, so that the standard IO is redirected in/out of sockets. As soon as
the server (which performs this redirection) executes the new program with
execv(), the client (who is listening on the sockets) gets a message that
the socket has been closed, and exits. This does not happen with
applications that have been written with cygwin32, but it does happen with
anything else (ftp.exe for example). Does anyone know what Windows Console
apps do when they start up? I am running 19.1 on NT 4.0, with egcs 1.0.2 and
the latest coolview (July 18, I think). If anyone wants more information,
let me know. Thanks in advance for the help...
Peter Mularski
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
reply other threads:[~1998-07-22 16:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000801bdb5ad$9192ab40$732ddd80@cpc45115.us.dg.com' \
--to=pmularski@clariion.com \
--cc=gnu-win32@cygnus.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).