Hi Gunnar, The first thing I found out is that it looks like a problem in QList and Event-Listeners.
> Thread 0 Crashed: > 0 <<00000000>> 0x26594a85 0 + 643385989 > 1 libqtjambi.jnilib 0x0275367e qtjambi_event_notify(void**) + 80 > 2 libQtCore.4.dylib 0x0896fd53 > QInternal::activateCallbacks(QInternal::Callback, void**) + 115 > 3 libQtCore.4.dylib 0x08a60b11 > QCoreApplication::notifyInternal(QObject*, QEvent*) + 49 > 4 libQtCore.4.dylib 0x08a63de1 > QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 689 > 5 libQtGui.4.dylib 0x08d4d68b > QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + > 107 > 6 libQtCore.4.dylib 0x08a60231 > QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 65 > 7 libQtCore.4.dylib 0x08a602fd > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 157 > 8 libQtCore.4.dylib 0x08a64021 QCoreApplication::exec() + 161 > 9 <<00000000>> 0x04590281 0 + 72942209 > 10 <<00000000>> 0x0458aa7f 0 + 72919679 > 11 <<00000000>> 0x0458a9d3 0 + 72919507 > 12 <<00000000>> 0x0458821f 0 + 72909343 > 13 libclient.dylib 0x9c0a0a6a jio_snprintf + 396484 > 14 libclient.dylib 0x9c0a07b8 jio_snprintf + 395794 > 15 libclient.dylib 0x9c0bcc5f JVM_MaxMemory + 7297 > 16 libclient.dylib 0x9c108bc4 JVM_FindLoadedClass + 2310 > 17 java 0x00003d10 0x1000 + 11536 > 18 java 0x000045c9 0x1000 + 13769 > 19 java 0x00001ee6 0x1000 + 3814 > 20 java 0x00001e0d 0x1000 + 3597 Tom Tom Schindl schrieb: > Hi Gunnar, > > Gunnar Sletta schrieb: >> Tom Schindl wrote: >>> Hi Gunnar, >>> >>> which IDE are you using for development? If you are using Eclipse I >>> could simply upload my workspace else I'll have to produce something >>> different. >> IDE? I use emacs & ant, primarily. Some IntelliJ and Eclipse, but very >> seldom ;) >> > > ah :-) > >>> The error occurs in an small Test-Application for my UFaceKit-Project so >>> the dependencies are quite big. >> I would apprechiate if you could narrow it down a little bit, at least >> bring it down to a single file, if that is possible ;) >> > > I'll try to give me best to come up with a reproduceable snippet of > code. The hard thing is to find out which part is failing if I'd have a > core dump, stack-trace, ... I have a point to start with but because it > only crashes without anything I'm a bit lost to find out where I need to > start. > > Tom > _______________________________________________ > Qt-jambi-interest mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
