From kdevelop-bugs  Tue Aug 31 13:33:11 2010
From: =?UTF-8?Q?Andr=C3=A1s=20Man=C5=A3ia=20?=<amantia () kde ! org>
Date: Tue, 31 Aug 2010 13:33:11 +0000
To: kdevelop-bugs
Subject: [Bug 249634] New: KDevelop crashes on project load
Message-Id: <bug-249634-40295 () http ! bugs ! kde ! org/>
X-MARC-Message: https://marc.info/?l=kdevelop-bugs&m=128326193632590

https://bugs.kde.org/show_bug.cgi?id=249634

           Summary: KDevelop crashes on project load
           Product: kdevelop
           Version: SVN
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: Build tools: CMake
        AssignedTo: kdevelop-bugs@kdevelop.org
        ReportedBy: amantia@kde.org


Version:           SVN (using Devel) 
OS:                Linux

When I load a (cmake, KDE) project or a session with those projects is
restored, KDevelop closes with an assert:
ASSERT failure in QCoreApplication::sendEvent: "Cannot send events to objects
owned by a different thread. Current thread c3cf40. Receiver '' (of type
'KDirWatchPrivate') was created in thread 61ae20", file
/home/andris/development/sources/kde-trunk/qt-copy/src/corelib/kernel/qcoreapplication.cpp,
line 349

This happens with kdelibs trunk an Qt 4.7 branch as of today, probably the
assert was added recently to Qt.

Andreas said this might be in a bug in the cmake part, so I file there.
Here is something I talked with David Faure on IRC:

[14:26] <andris> i get this on kdevelop startup (compiled for an older kdelibs
trunk, and running on trunk from today, qt 4.7 branch):
[14:26] <andris> ASSERT failure in QCoreApplication::sendEvent: "Cannot send
events to objects owned by a different thread. Current thread c6c200. Receiver
'' (of type 'KDirWatchPrivate') was created in thread 61ae20", file
/home/andris/development/sources/kde-trunk/qt-copy/src/corelib/kernel/qcoreapplication.cpp,
line 349
[14:26] <andris> Unable to start Dr. Konqi
[14:27] <andris> KDirWatch bug or Qt issue?
[14:28] <dfaure> ... or kdevelop using kdirwatch acorss threads?
[14:29] <andris> kdirwatch is not thread safe?
[14:29] <dfaure> I suppose that an instance in each thread should work, but
using the same instance across threads hasn't been tested/fixed, no
[14:29] <dfaure> funny how everyone assumes that everything in kdelibs is
magically threadsafe :-)
[14:30] <dfaure> it can be made so, but someone has to ;)




Reproducible: Always

-- 
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