From: Eric Hodel <drbrain@...7.net>
Date: 2004-08-18T13:39:35+09:00
Subject: Re: WEBrick deadlock under Cygwin

--TKYYegg/GYAC5JIZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Florian Gross (flgr@ccan.de) wrote:

> Eric Hodel wrote:
>=20
> >The right (wrong) sequence of locking can easily create a deadlock in
> >the right circumstances.  I can generate a deadlock easily in Borges due
> >to do an incorrect sequence of locks after an exception kills a thread.
> >(The exception is only important because it allows the threads to
> >deadlock.)
>=20
> But isn't this considered a Ruby bug?

No, this is definetly my bug.  If a developer can't synchronize threads
properly, how can Ruby determine the correct way?

--=20
Eric Hodel - drbrain@segment7.net - http://segment7.net
All messages signed with fingerprint:
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04


--TKYYegg/GYAC5JIZ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQFBIt2FMypVHHlsnwQRAn15AKCS9sUKC08m0Dv7zH2GTQZAqzxHYgCghm/z
ZiSpJGZB/Qd7HpHot3U/lnM=
=tf+p
-----END PGP SIGNATURE-----

--TKYYegg/GYAC5JIZ--