We have done some long-term observations both with kvats and qutecom. In most cases, freeze happens after a longer suspend period. This annoys all people, who run kvats or qutecom on a laptop, and this will be the majority of users.
After some discussions with Laurent in Krems, it seems like a deadlock between boost and Qt. How can we debug this? Neither gdb does not throw any useful information nor do we have an indicator in the log files with OWLOGGER_DEFAULT set to 0. Can we turn on debugging for the semaphores? Our observation is, that a network change does most time not result in a freeze, however, SIP does not re-connect properly in most cases. --RAS -- Roland Alton-Scheidl Member of the Board http://osAlliance.com [EMAIL PROTECTED] M +43 664 1547588 Marktstrasse 4 A-6850 Dornbirn FN 218498x HG Wien _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
