From: Eric Blake <ebb9@byu.net>
To: The Quality-Schmality List <cygwin-talk@cygwin.com>
Subject: Re: FW: cygwin-1.dll long-time bug
Date: Wed, 19 Apr 2006 03:44:00 -0000 [thread overview]
Message-ID: <4445B212.7000400@byu.net> (raw)
In-Reply-To: <002e01c66317$581533e0$a501a8c0@CAM.ARTIMI.COM>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Dave Korn on 4/18/2006 12:38 PM:
>
> Well, I think it's reasonable enough to say that cygwin does things that are
> pushing the envelope of what's documented to work in relation to how we handle
> forking and process startup. After all we just had that lockup caused by the
> fact that you can't even call GetModuleName[*] from DllMain safely. Things
> happen in an unusual order in cygwin processes and threads, and it's probably
> not something that gets a whole load of testing in microsoft's QA dept.... ;)
They have one? What are the job qualifications to become a member of that
dept, I wonder? I bet even a hippo could apply...
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFERbIR84KuGfSFAYARAp2kAJ0Y+cRPD4HKcenYj/LkQLiwI7/PHgCgw249
fWsG0xVksjucwkn3aZJhbUM=
=sfVh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-04-19 3:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 18:13 Dave Korn
2006-04-18 18:25 ` Christopher Faylor
2006-04-18 18:38 ` Dave Korn
2006-04-19 2:26 ` Gary R. Van Sickle
2006-04-19 17:06 ` Christopher Faylor
2006-04-19 18:01 ` Dave Korn
2006-04-19 3:44 ` Eric Blake [this message]
2006-04-19 8:28 ` Dave Korn
2006-04-19 12:58 ` Igor Peshansky
2006-04-19 13:46 ` Dave Korn
2006-04-28 9:10 ` Ludovic Drolez
2006-04-19 13:47 Williams, Gerald S (Jerry)
2006-04-19 14:03 ` Igor Peshansky
2006-04-19 14:04 ` Dave Korn
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=4445B212.7000400@byu.net \
--to=ebb9@byu.net \
--cc=cygwin-talk@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).