Deadlock
David Nolden
david.nolden.kdevelop at art-master.de
Wed Jun 24 21:24:51 UTC 2009
Am Mittwoch 24 Juni 2009 21:26:25 schrieb Milian Wolff:
> David Nolden, 24.06.2009:
> > Am Dienstag 23 Juni 2009 13:53:51 schrieb Milian Wolff:
> > > Hey guys, just got a deadlock:
> > >
> > > http://pastebin.com/m77d9ba0f
> > >
> > > Zwabel, can you do something with that?
> >
> > It's fixed now.
>
> Thanks, but I got another one. Opened Kdevelop with KDevplatform as project
> and started to hack rightaway while in the background lots of files were
> processed. Backtrace is here:
>
> http://pastebin.com/m289af8a5
The problem is in the control flow graph here. It tries to lock the duchain
from within a directly received signal from ktexteditor. The editor smart-
mutex is locked within such signals, and this it will lead to a deadlock when
the use-builder tries to lock the smart-mutex while already holding the smart-
lock.
It is generally forbidden to lock the duchain after locking the smart-mutex,
the order must always be the other way around.
Simple solution in this case: Use a queued connection to deliver the signal.
Greetings, David
More information about the KDevelop-devel
mailing list