Re: [Boost-users] Troubleshooing deadlock with upgrade_lock<shared_mutex>

Subject: Re: [Boost-users] Troubleshooing deadlock with upgrade_lock<shared_mutex>
From: Frank Mori Hess (frank.hess_at_[hidden])
Date: 2010-04-23 13:57:11

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 23 April 2010, Ken Smith wrote:
> Periodically, the app stops responding.  When it does, I can see that the
> transmit() method is working fine, but the createRoom() and deleteRoom()
> methods (on separate threads, obviously) appear to be deadlocked on the
> highlighted lines, waiting to acquire their upgrade_locks.

> Am I doing something wrong?  Any suggestions on troubleshooting this?

Yes, they are deadlocked because both upgrade locks are waiting for the other 
to release shared ownership so they can upgrade to unique ownership.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkvR33cACgkQ5vihyNWuA4XoTwCgrpAjRxmzjOcQP4J6rW4v0gpZ
bOEAoJ/5V8nO3AO6Fbo8PlJaE+z0pTAc
=qXzk
-----END PGP SIGNATURE-----