From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Threaded Cygwin Python Import Problem
Date: Wed, 18 Jul 2001 17:09:00 -0000 [thread overview]
Message-ID: <20010718200853.A5083@redhat.com> (raw)
In-Reply-To: <3B56201A.8137A41E@nc.rr.com>
On Wed, Jul 18, 2001 at 07:47:38PM -0400, Greg Smith wrote:
>
>I think I've recreated Jason's threaded Python problem after fork(),
>see the testcase below. And this is on my w2k sp2 dual pIII 850
>machine, where I have been unsuccessful in recreating Jason's
>original Python testcase.
>
>I certainly do not claim Cygwin expertise, nor Windows API expertise,
>and not as much *ix as I'd like (ask me about os/390, however, and
>I'll give you a different story ;-).
>
>But, it looks like fork_copy() blindly copies everything from the
>original process address space to the new address space, including
>any pthread_mutex_t structures. And neither __pthread_mutex_lock
>nor WaitForSingleObject() recognize that the mutex is not properly
>initialized. If the comments in the testcase are removed (ie clear
>the lock and initialize it), then the testcase runs as expected.
If that is the case then a "fixup_after_fork" routine is probably
required. You can see several of those in fork.cc.
cgf
--
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/
next prev parent reply other threads:[~2001-07-18 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 16:46 Greg Smith
2001-07-18 17:09 ` Christopher Faylor [this message]
2001-07-18 17:47 ` Greg Smith
2001-07-18 17:56 Robert Collins
2001-07-18 18:08 Robert Collins
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=20010718200853.A5083@redhat.com \
--to=cgf@redhat.com \
--cc=cygwin@cygwin.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).