[Mono-bugs] [Bug 55909][Wis] Changed - Deadlock in ReaderWriterLock.UpgradeToWriterLock()

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by lluis@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=55909

--- shadow/55909	2004-04-10 10:22:22.000000000 -0400
+++ shadow/55909.tmp.5221	2004-04-11 11:21:12.000000000 -0400
@@ -199,6 +199,20 @@
 seems to be complete ... ;)
 
 ------- Additional Comments From mono-bug@jerryweb.info  2004-04-10 10:22 -------
 Created an attachment (id=7309)
 Patch for next deadlock. Grrrrr...:-(((
 
+
+------- Additional Comments From lluis@ximian.com  2004-04-11 11:21 -------
+Dude, I think that my code deserves a little more respect. I've spent
+a couple of hours doing a full review of ReaderWriterLock, checking
+its behavior in MS.NET, and writing unit tests. I don't see the need
+for a rewrite. I we were to rewrite a class every time we find a bug
+we would never finish the project.
+
+I found the origin of your "The thread does not have any reader or
+writer locks" exception. It was a 3 lines fix. Please, update from CVS
+and try again.
+
+And regarding the DowngradeFromWriter deadlock you mentioned, please
+attach a test case.