tag:blogger.com,1999:blog-4863981320393275450.post7602080785489708083..comments2008-09-06T01:08:31.116+03:00Comments on The Typemock Insider Blog: Finding Deadlocks with ReaderWriterLock and Typemo...Gil Zilberfeldhttps://profiles.google.com/109599652166509206604noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-4863981320393275450.post-46358973865754145822008-09-06T01:08:00.000+03:002008-09-06T01:08:00.000+03:00It will block because it waits for the other threa...It will block because it waits for the other thread to release its reader lock. No need for a second lock.Omer Mornoreply@blogger.comtag:blogger.com,1999:blog-4863981320393275450.post-1165454558237169692008-09-05T12:46:00.000+03:002008-09-05T12:46:00.000+03:00Omer, <br>the lock() is required for a deadlock so...Omer, <BR/>the lock() is required for a deadlock so that one thread will block waiting for the other one to release.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4863981320393275450.post-38389921315964679562008-09-05T11:00:00.000+03:002008-09-05T11:00:00.000+03:00I think the monitor lock ("lock (sync)")...I think the monitor lock ("lock (sync)") is not needed for this deadlock to occur. A simple "acquire read" --> "acquire write" approach would suffice.<BR/><BR/>-- OmerOmer Mornoreply@blogger.comtag:blogger.com,1999:blog-4863981320393275450.post-33344329154471241382008-09-05T10:58:00.000+03:002008-09-05T10:58:00.000+03:00This comment has been removed by the author.Omer & Noahttp://www.blogger.com/profile/05524751715995551821noreply@blogger.com