On terça-feira, 21 de agosto de 2012 11.17.18, Igor Mironchik wrote: > > On terça-feira, 21 de agosto de 2012 11.04.14, Igor Mironchik wrote: > >> I'm playint with this issue. And notice that the problem is not played > >> too often. > >> Sometimes slotDisconnected() not invoked in general. What is problem too. > >> But when he invoked I have stable dead-lock. What is the reason? App is > >> one-threaded. > > > > A deadlock in a one-threaded application usually implies that you tried to > > lock twice a non-recursive mutex. > > I understand it. > > > Look at your backtrace and figure out what the other lock point was. > > But just imagine a situation in which the potential for double locking > in a one-threaded environment is posiible. > It is not possible at all. But I see that when executing > ServerSocket::doThis() sometimes method ServerSocket::slotDisconnected() > is called asynchronously, so to speak. I.e. in the middle of > ServerSocket::doThis() invoked ServerSocket::slotDisconnected(). How > it's possible in one-threaded app?
It's possible because you called a function that can call that slot.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/interest
