Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
Fellows: I took some extra time to test the different branches currently available ( and relevant ) to these issues: 1) master and 2.0.0-beta -> Refusal to build issuing the following compilation error: ../../../../qt-creator/src/plugins/qmlprojectmanager/qmlproject.cpp: In member function ‘void QmlProjectManager::QmlProject::parseProject(QFlags)’: ../../../../qt-creator/src/plugins/qmlprojectmanager/qmlproject.cpp:103: error: ‘class QDeclarativeComponent’ has no member named ‘errorsString’ make[3]: *** [.obj/debug-shared/qmlproject.o] Error 1 make[3]: *** Waiting for unfinished jobs make[2]: *** [sub-qmlprojectmanager-make_default] Error 2 make[1]: *** [sub-plugins-make_default-ordered] Error 2 make: *** [sub-src-make_default-ordered] Error 2 2) 2.0 and 2.0.0 -> Compiled and run, but still both of them crash when creating a new object via the wizard. See the trace enclosed at the end for the details (not different from the ones already sent via email). 3) qtcreator-mac-opensource-2.0.0-rc1.dmg -> Works find, without crashes. And yes, I had to resort to the packaged (and much bigger bundle) simply because I had already blew away the old QtCreator I had installed and worked fine under the assumption that a new compiled version should work OK... :-( Best regards, Victor = Process: Qt Creator [44983] Path:/Users/vsardina/Downloads/Qt/qtcreatorbuild/bin/Qt Creator.app/Contents/MacOS/Qt Creator Identifier: com.nokia.qtcreator Version: 1.3.85 (1.3.85) Code Type: X86-64 (Native) Parent Process: launchd [179] Date/Time: 2010-06-14 00:26:08.933 -1000 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x7fff864d4886 __kill + 10 1 libSystem.B.dylib 0x7fff86574eae abort + 83 2 QtCore 0x000100ed0685 qt_message_output(QtMsgType, char const*) + 117 3 QtCore 0x000100ed0867 qt_message(QtMsgType, char const*, __va_list_tag*) + 183 4 QtCore 0x000100ed0a2a qFatal(char const*, ...) + 170 5 QtCore 0x000100f673a1 QtSharedPointer::ExternalRefCountData::setQObjectShared(QObject const*, bool) + 49 6 libCore_debug.dylib 0x000115318dd0 QtSharedPointer::ExternalRefCount::internalFinishConstruction(QWizard*) + 58 (qsharedpointer_impl.h:368) 7 libCore_debug.dylib 0x000115318e22 QtSharedPointer::ExternalRefCount::internalConstruct(QWizard*) + 80 (qsharedpointer_impl.h:344) 8 libCore_debug.dylib 0x000115318e56 QSharedPointer::QSharedPointer(QWizard*) + 44 (qsharedpointer_impl.h:449) 9 libCore_debug.dylib 0x000115315cab Core::BaseFileWizard::runWizard(QString const&, QWidget*) + 611 (basefilewizard.cpp:509) 10 libCore_debug.dylib 0x00011526cb65 Core::Internal::MainWindow::showNewItemDialog(QString const&, QList const&, QString const&) + 637 (mainwindow.cpp:905) 11 libCore_debug.dylib 0x00011526d6de Core::Internal::MainWindow::newFile() + 82 (mainwindow.cpp:778) 12 libCore_debug.dylib 0x00011535182a Core::Internal::MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 324 (moc_mainwindow.cpp:129) 13 QtCore 0x000100f25dce QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1694 14 QtGui 0x00010014a591 QAction::triggered(bool) + 49 15 QtGui 0x00010014d3f9 QAction::qt_metacall(QMetaObject::Call, int, void**) + 601 16 QtCore 0x000100f25dce QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1694 17 QtGui 0x00010014a591 QAction::triggered(bool) + 49 18 QtGui 0x00010014b974 QAction::activate(QAction::ActionEvent) + 180 19 QtGui 0x000100101d1a -[QCocoaMenuLoader qtDispatcherToQAction:] + 106 20 com.apple.AppKit0x7fff883fc8ea -[NSApplication sendAction:to:from:] + 95 21 com.apple.AppKit0x7fff88420e5a -[NSMenuItem _corePerformAction] + 365 22 com.apple.AppKit0x7fff88420bc4 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 121 23 com.apple.AppKit0x7fff886a493d -[NSMenu _internalPerformActionForItemAtIndex:] + 35 24 com.apple.AppKit0x7fff88556729 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerC
Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
Hi, On Mon, Jun 14, 2010 at 12:30 PM, wrote: > qmldump is in src/tools, and isn't something we regularly maintain. It's just > a helper program that we fix from time to time, when we need it :) Anyhow, it > shouldn't be compiled by default ... Did you manually go to src/tools/qmldump > and ran qmake? No, since last Thursday - Qt Creator gitorious master branch tries to compile qmldump on every rebuild. Without any addition options etc. And as it was described - due to bugs it stop a full build. -- Best Regards, Denis Mingulov ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
qt-creator-boun...@trolltech.com wrote: > [...] > I tried to compile it yesterday too and got similar errors, > but in my case on Linux and when it compiled some "qmldump" > tool. qmldump is in src/tools, and isn't something we regularly maintain. It's just a helper program that we fix from time to time, when we need it :) Anyhow, it shouldn't be compiled by default ... Did you manually go to src/tools/qmldump and ran qmake? > The .pro file(s) apparently miss some include paths and > the whole issue comes from that the developers only build Qt > as a "developer build", they never test with a Qt that has > been "make install":ed. The latter is IMHO the default way of working > for normal users. Well, the problem is probably rather that we use in the Qml support (and qmldump) some private headers, which isn't really supported in Qt when you're using the install step (see README). > I will report bugs as soon as the bug thingie comes back online. Regarding qmldump: I'm happy to accept patches for this, but as I said: It's not something we expect people to compile/use, so fixing it just for the heck of it won't have any priority. Regards Kai -- Kai Köhne Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
On Monday 14 June 2010, Victor Sardina wrote: > Tobias: > > I should have added "when the bugreports site comes back online". It > hasn't come back in line as yet. > > By the way, I tried to recompile QtCreator from the master branch and > got a whole bunch of errors like: > > /usr/local/Trolltech/Qt-4.8.0/lib/QtDeclarative.framework/Versions/4/Header > s/qdeclarativeengine.h:62: error: forward declaration of ‘const struct > QDeclarativeType’ > > I just recompiled and installed the latest Qt libraries from the master > branch, so I cannot figure out the reason behind the errors. I tried to compile it yesterday too and got similar errors, but in my case on Linux and when it compiled some "qmldump" tool. The .pro file(s) apparently miss some include paths and the whole issue comes from that the developers only build Qt as a "developer build", they never test with a Qt that has been "make install":ed. The latter is IMHO the default way of working for normal users. I will report bugs as soon as the bug thingie comes back online. -- Jan Ekholm jan.ekh...@smultron.net ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
Tobias: I should have added "when the bugreports site comes back online". It hasn't come back in line as yet. By the way, I tried to recompile QtCreator from the master branch and got a whole bunch of errors like: /usr/local/Trolltech/Qt-4.8.0/lib/QtDeclarative.framework/Versions/4/Headers/qdeclarativeengine.h:62: error: forward declaration of ‘const struct QDeclarativeType’ I just recompiled and installed the latest Qt libraries from the master branch, so I cannot figure out the reason behind the errors. Best regards, Victor On 6/13/10 9:45 PM, Tobias Hunger wrote: > On 14.06.2010 07:13, ext Victor Sardina wrote: >> Fellows: >> >> I recompiled the latest Qt master branch as well as the latest QtCreator >> 2.0 branch after pulling all the latest changes as of today. The crash >> still happens, as shown in the trace below. I will try some other branch >> to see if I can get rid of this, maybe 2.0.0-beta? > > Hi Victor! > > Did you file a bugreport at http://bugreports.qt.nokia.com/ (which seems > to be down at this time?) already? > > Reports to the mailing list sometimes get overlooked with everybody > being busy fixing reported bugs for the release;-) > > Best Regards, > Tobias > > <>___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
Hi Tobias: Not really. I haven't filed a bug report yet (just laziness I guess). I will drop a bug report regarding this issue, as you suggested. As long as it does not get through the cracks... Best regards, Victor On 6/13/10 9:45 PM, Tobias Hunger wrote: > On 14.06.2010 07:13, ext Victor Sardina wrote: >> Fellows: >> >> I recompiled the latest Qt master branch as well as the latest QtCreator >> 2.0 branch after pulling all the latest changes as of today. The crash >> still happens, as shown in the trace below. I will try some other branch >> to see if I can get rid of this, maybe 2.0.0-beta? > > Hi Victor! > > Did you file a bugreport at http://bugreports.qt.nokia.com/ (which seems > to be down at this time?) already? > > Reports to the mailing list sometimes get overlooked with everybody > being busy fixing reported bugs for the release;-) > > Best Regards, > Tobias > > <>___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
Re: [Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
On 14.06.2010 07:13, ext Victor Sardina wrote: > Fellows: > > I recompiled the latest Qt master branch as well as the latest QtCreator > 2.0 branch after pulling all the latest changes as of today. The crash > still happens, as shown in the trace below. I will try some other branch > to see if I can get rid of this, maybe 2.0.0-beta? Hi Victor! Did you file a bugreport at http://bugreports.qt.nokia.com/ (which seems to be down at this time?) already? Reports to the mailing list sometimes get overlooked with everybody being busy fixing reported bugs for the release;-) Best Regards, Tobias -- Tobias Hunger Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ___ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
[Qt-creator] Crash persists even when recompiling the latest Qt and QtCreator Source Code.
Fellows: I recompiled the latest Qt master branch as well as the latest QtCreator 2.0 branch after pulling all the latest changes as of today. The crash still happens, as shown in the trace below. I will try some other branch to see if I can get rid of this, maybe 2.0.0-beta? Regards, Victor === Process: Qt Creator [38773 Path:/Users/vsardina/Downloads/Qt/qtcreatorbuild/bin/Qt Creator.app/Contents/MacOS/Qt Creator Identifier: com.nokia.qtcreator Version: 2.0.80 (2.0.80) Code Type: X86-64 (Native) Parent Process: launchd [179] Date/Time: 2010-06-13 19:07:16.563 -1000 OS Version: Mac OS X 10.6.3 (10D573) Report Version: 6 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Crashed Thread: 0 Dispatch queue: com.apple.main-thread Application Specific Information: abort() called Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0x7fff864d4886 __kill + 10 1 libSystem.B.dylib 0x7fff86574eae abort + 83 2 QtCore 0x000100ed0685 qt_message_output(QtMsgType, char const*) + 117 3 QtCore 0x000100ed0867 qt_message(QtMsgType, char const*, __va_list_tag*) + 183 4 QtCore 0x000100ed0a2a qFatal(char const*, ...) + 170 5 QtCore 0x000100f673a1 QtSharedPointer::ExternalRefCountData::setQObjectShared(QObject const*, bool) + 49 6 libCore_debug.dylib 0x000114946af4 QtSharedPointer::ExternalRefCount::internalFinishConstruction(QWizard*) + 58 (qsharedpointer_impl.h:368) 7 libCore_debug.dylib 0x000114946b46 QtSharedPointer::ExternalRefCount::internalConstruct(QWizard*) + 80 (qsharedpointer_impl.h:344) 8 libCore_debug.dylib 0x000114946b7a QSharedPointer::QSharedPointer(QWizard*) + 44 (qsharedpointer_impl.h:449) 9 libCore_debug.dylib 0x0001149439d7 Core::BaseFileWizard::runWizard(QString const&, QWidget*) + 611 (basefilewizard.cpp:510) 10 libCore_debug.dylib 0x00011489a359 Core::Internal::MainWindow::showNewItemDialog(QString const&, QList const&, QString const&) + 637 (mainwindow.cpp:910) 11 libCore_debug.dylib 0x00011489aed2 Core::Internal::MainWindow::newFile() + 82 (mainwindow.cpp:783) 12 libCore_debug.dylib 0x0001149827f2 Core::Internal::MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 324 (moc_mainwindow.cpp:129) 13 QtCore 0x000100f25dce QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1694 14 QtGui 0x00010014a591 QAction::triggered(bool) + 49 15 QtGui 0x00010014d3f9 QAction::qt_metacall(QMetaObject::Call, int, void**) + 601 16 QtCore 0x000100f25dce QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 1694 17 QtGui 0x00010014a591 QAction::triggered(bool) + 49 18 QtGui 0x00010014b974 QAction::activate(QAction::ActionEvent) + 180 19 QtGui 0x000100101d1a -[QCocoaMenuLoader qtDispatcherToQAction:] + 106 20 com.apple.AppKit0x7fff883fc8ea -[NSApplication sendAction:to:from:] + 95 21 com.apple.AppKit0x7fff88420e5a -[NSMenuItem _corePerformAction] + 365 22 com.apple.AppKit0x7fff88420bc4 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 121 23 com.apple.AppKit0x7fff886a493d -[NSMenu _internalPerformActionForItemAtIndex:] + 35 24 com.apple.AppKit0x7fff88556729 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 136 25 com.apple.AppKit0x7fff884033b0 NSSLMMenuEventHandler + 321 26 com.apple.HIToolbox 0x7fff82f61b57 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1002 27 com.apple.HIToolbox 0x7fff82f610a6 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 395 28 com.apple.HIToolbox 0x7fff82f7ed85 SendEventToEventTarget + 45 29 com.apple.HIToolbox 0x7fff82fade61 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 387 30 com.apple.HIToolbox 0x7fff82fdabf6 SendMenuCommandWithContextAndModifiers + 56 31 com.apple.HIToolbox 0x7fff82fdabae SendMenuItemSelectedEvent + 101 32 com.apple.HIToolbox 0x7fff82fdaabe FinishMenuSelection(SelectionData*,