another crash

[Aleix]

Ok, I found the problem.

Instead of including "myfile.moc" i was including "myfile.cpp", yeah, silly
I know.

maybe you would want to prevent this to block the cpu in some way.

thanks,
Aleix

On Fri, Jul 11, 2008 at 8:10 PM, Aleix <aleixpol at gmail.com> wrote:

> This is not a crash but a dead lock... at least seemed so, I'm not sure
> (but it took the CPU 99% and it didn't finish)
>
> hope it helps more than the other one.
>
> (gdb) where
> #0  0xb7fe3424 in __kernel_vsyscall ()
> #1  0xb62c1dc6 in nanosleep () from /lib/i686/cmov/libc.so.6
> #2  0xb62ff14c in usleep () from /lib/i686/cmov/libc.so.6
> #3  0xb61ea38a in KDevelop::DUChainLock::lockForRead (this=0x9645aa8,
> timeout=40000) at
> /home/kde-devel/kdevplatform/language/duchain/duchainlock.cpp:168
> #4  0xb61ea575 in KDevelop::DUChainReadLocker::lock (this=0xbfafbc54) at
> /home/kde-devel/kdevplatform/language/duchain/duchainlock.cpp:348
> #5  0xb61ea610 in DUChainReadLocker (this=0xbfafbc54,
> duChainLock=0x9645aa8, timeout=0) at
> /home/kde-devel/kdevplatform/language/duchain/duchainlock.cpp:329
> #6  0xb3d10de1 in ClassModel::branchModified (this=0x95e1930, context={d =
> {d = 0xbfafbcc8}})
>     at /home/kde-devel/kdevplatform/plugins/classbrowser/classmodel.cpp:503
> #7  0xb3d111bc in ClassModel::qt_metacall (this=0x95e1930,
> _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x9fe43fb0)
>     at
> /home/kde-devel/build-kdevplatform/plugins/classbrowser/classmodel.moc:75
> #8  0xb7430306 in QMetaCallEvent::placeMetaCall (this=0x9fe43cc0,
> object=0x95e1930) at kernel/qobject.cpp:535
> #9  0xb7434694 in QObject::event (this=0x95e1930, e=0x9fe43cc0) at
> kernel/qobject.cpp:1128
> #10 0xb68830f9 in QApplicationPrivate::notify_helper (this=0x94a46c0,
> receiver=0x95e1930, e=0x9fe43cc0) at kernel/qapplication.cpp:3766
> #11 0xb6883412 in QApplication::notify (this=0xbfafc54c,
> receiver=0x95e1930, e=0x9fe43cc0) at kernel/qapplication.cpp:3360
> #12 0xb78bca4b in KApplication::notify (this=0xbfafc54c,
> receiver=0x95e1930, event=0x9fe43cc0) at
> /home/kde-devel/kdelibs/kdeui/kernel/kapplication.cpp:311
> #13 0xb74216aa in QCoreApplication::notifyInternal (this=0xbfafc54c,
> receiver=0x95e1930, event=0x9fe43cc0) at kernel/qcoreapplication.cpp:583
> #14 0xb7abea1d in QCoreApplication::sendEvent () from
> /home/kde-devel//kde/lib/libphonon.so.4
> #15 0xb7421bc2 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0,
> event_type=0, data=0x945f538) at kernel/qcoreapplication.cpp:1195
> #16 0xb7421d73 in QCoreApplication::sendPostedEvents (receiver=0x0,
> event_type=0) at kernel/qcoreapplication.cpp:1091
> #17 0xb7452446 in QCoreApplication::sendPostedEvents () at
> ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
> #18 0xb7451657 in postEventSourceDispatch (s=0x94a5da8) at
> kernel/qeventdispatcher_glib.cpp:211
> #19 0xb5d86278 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> #20 0xb5d89913 in ?? () from /usr/lib/libglib-2.0.so.0
>
>
>
> On Fri, Jul 11, 2008 at 11:35 AM, David Nolden <zwabel+kde at gmail.com<zwabel%2Bkde at gmail.com>>
> wrote:
>
>> Am Freitag, 11. Juli 2008 10:48:37 schrieb Aleix:
>> > KDevelop4 is crashing here when loading kdevelop while parsing the files
>> i
>> > already had open.
>> >
>> > If you need more info just tell me.
>> >
>> > cheers!
>> >
>> > aleix
>>
>> As written on chat, delete the old usehighlight plugin from your
>> installation
>> directory, and it should work. :)
>>
>> Greetings, David
>>
>> _______________________________________________
>> KDevelop-devel mailing list
>> KDevelop-devel at kdevelop.org
>> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20080711/6a552664/attachment.html>