On Oct 10, Guilhem Bichot wrote:
> Why don't the two threads wanting the rwlock get this rwlock? The
> read-locker is the 8th recursive call to deadlock_search(); it wants
> 38d8b4 (hex address of rwlock), but it already has read-locked those
> others rwlocks in previous calls of the recursion
> (waiting_threads.c:419): 38e638, 38d898, 38e638, 38afe8, 38dd38,
> 38a6d0, 3875c8.
> This does not include the wanted rwlock.
> So, I don't know.
> Maybe it is the deadlock which you feared on certain rwlock
> implementations? Note that Windows build is using our home-made
> thr_rwlock.c implementation.
Yes, looks like it's the one.
Regards / Mit vielen Grüßen,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Sergei Golubchik <serg@stripped>
/ /|_/ / // /\ \/ /_/ / /__ Principal Software Engineer/Server Architect
/_/ /_/\_, /___/\___\_\___/ Sun Microsystems GmbH, HRB München 161028
<___/ Sonnenallee 1, 85551 Kirchheim-Heimstetten
Geschäftsführer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Häring