[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 252659] deadlock due to ForegroundLock
From: David Nolden <david.nolden.kde () art-master ! de>
Date: 2010-12-01 16:58:03
Message-ID: 20101201165803.21360763F1 () immanuel ! kde ! org
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=252659
--- Comment #8 from David Nolden <david nolden kde art-master de> 2010-12-01 17:58:00 ---
I've encountered this deadlock again, and did some debugging within QMutex.
I've found out that QMutex ends up waiting for a wait-condition, while there is
no other thread holding the mutex (d->owner == 0), so there is noone to wake
the thread up from the wait-condition.
I've changed the code to use a pthread mutex directly now. If it happens again
with the pthread mutex, then it should be a clear sign that the problem is on
our side. If it doesn't happen again with the pthread mutex, then it's a QMutex
bug.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic