This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: fcntl(F_SETFD) on a file or socket handle
On Thu, Sep 20, 2001 at 04:46:47PM +0900, Dmitry Timoshkov wrote:
> "Corinna Vinschen" <cygwin@cygwin.com> wrote:
>
> > > Analyzing Cygwin code, it seems I have found the source of the problem (had no
> > > time to confirm it running offending code though).
> > >
> > > It's in the fhandler_base::set_inheritance() called from fhandler_base::set_close_on_exec().
> > >
> > > DuplicateHandle()/CloseHandle() invalidates original system handle associated
> > > with the Cygwin internal file descriptor (fd) while an operation on the fd is
> > > possibly still in progress.
> >
> > Thanks for the hint.
> >
> > That should unlikely be the cause, except you're running plain win95.
> > If you take a look into fhandler_socket.cc, you'll see that the
> > fhandler_socket class defines it's own set_close_on_exec() method
> > which doesn't call set_inheritance() when running Winsock2.
>
> I see that fhandler_socket::fcntl() calls fhandler_base::fcntl() in
> all cases different from F_SETFL. Perhaps my understanding of things
> in C++ is not enough (I'm an old hand plain C programmer).
set_close_on_exec() is a virtual method which means, the called
method is dependent of the actual class of the object which calls
it. Did you get the sources of Cygwin via CVS? If so, could
you please check if my just checked in patch works for you?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/