Finding Deadlocks with ReaderWriterLock and Typemock Racer

My blog has moved. You can view this post at the following address: http://www.osherove.com/blog/2008/9/4/finding-deadlocks-with-readerwriterlock-and-typemock-racer.html
Published Thursday, September 04, 2008 9:06 PM by RoyOsherove
Filed under: , , , , ,

Comments

Thursday, September 04, 2008 9:16 PM by funny wallpaper » Finding Deadlocks with ReaderWriterLock and Typemock Racer

# funny wallpaper » Finding Deadlocks with ReaderWriterLock and Typemock Racer

Pingback from  funny wallpaper » Finding Deadlocks with ReaderWriterLock and Typemock Racer

Friday, September 05, 2008 3:50 PM by IHateSpaghetti {code}

# Blog Carnival #4

DSL Tools DSL Tools SP1 features - Nested shapes and improvements - by Jean-Marc Web Firefox, ClickOnce

Wednesday, September 10, 2008 2:59 PM by Stuart Carnie

# re: Finding Deadlocks with ReaderWriterLock and Typemock Racer

Yes, thread1 and thread2 get reader locks, thread1 also gets an exclusive lock on the 'sync' and thread2 is blocked on the call to 'sync'.  thread1 attempts to upgrade to a writer lock, but is blocked because thread2 is holding a readerlock, which in turn is blocked because it is waiting for the sync to be released.