[Qt4-preview-feedback] Buildkey does not contains carbon/cocoa on Mac

[Axel Jäger]

Ooops, this one went to trenton in private mail...

Hi,
my motivation is: Qt was generally picky on what plugins to load so I  
wanted to give it several versions to pick one from so my user likely  
does not have to compile an own plugin. Also I did not want my user  
dig around which version of my software he has to download. Also I did  
not want my user to have several versions of my app installed for  
several Qt versions because I prefer to have around 3 versions or so  
of Qt on my system. So for me, including the configuration in the  
buildkey would greatly improve the download and it just works  
experience.

So here is the crash log:

0   libSystem.B.dylib             	0x95f34e42 __kill + 10
1   libSystem.B.dylib             	0x95fa723a raise + 26
2   libSystem.B.dylib             	0x95fb3679 abort + 73
3   QtCore                        	0x129d1235  
qt_message_output(QtMsgType, char const*) + 149
4   QtCore                        	0x129d1329 qFatal(char const*, ...)  
+ 105
5   QtGui                         	0x130b63ce qt_pixmap_thread_test()  
+ 94
6   QtGui                         	0x130b661d QPixmap::QPixmap(int,  
int) + 45
7   QtGui                         	0x12ff084a  
QMacStylePrivate::generateBackgroundPattern() const + 42
8   QtGui                         	0x12ff0e50  
QMacStyle::polish(QPalette&) + 576
9   QtGui                         	0x00b0e514  
QApplicationPrivate::setPalette_helper(QPalette const&, char const*,  
bool) + 68
10  QtGui                         	0x00b0ea40  
QApplication::setPalette(QPalette const&, char const*) + 32
11  QtGui                         	0x00b0ead6  
QApplicationPrivate::setSystemPalette(QPalette const&) + 134
12  QtGui                         	0x00b10903 QApplication::style() +  
547
13  QtGui                         	0x00aab5c4  
qt_mac_update_os_settings() + 804
14  QtGui                         	0x00aaefb3  
qt_init(QApplicationPrivate*, int) + 1811
15  QtGui                         	0x00b10b7d  
QApplicationPrivate::construct() + 77
16  QtGui                         	0x00b10ee3  
QApplication::QApplication(int&, char**, int) + 99

And here is what it says on the commandline:

QObject::moveToThread: Current thread (0x630640) is not the object's  
thread (0x609d30).
Cannot move to target thread (0x609d30)

On Mac OS X, you might be loading two sets of Qt binaries into the  
same process. Check that all plugins are compiled against the right Qt  
binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of  
binaries are being loaded.
[WARNING]QObject::startTimer: QTimer can only be used with threads  
started with QThread
QObject::setParent: Cannot set parent, new parent is in a different  
thread
[FATAL]QPixmap: Must construct a QApplication before a QPaintDevice
Abort trap

Best regards
Axel Jäger


Am 16.03.2009 um 09:30 schrieb Trenton Schulz:

> On 2009-03-14 17:12:11 +0100, Axel Jäger <axel.jaeger at basyskom.de>  
> said:
>
>> Hi,
>> I develop a plugin and over the years I got used to the very
>> conservative Qt plugin loader that only loads a plugin when it is
>> absolutely sure that the plugin will fit into the application testing
>> buildkey, configuration, version or whatever.
>>
>> Now I have two versions of Qt on my mac: One built with carbon, the
>> other one with cocoa and I see that my cocoa application tries to  
>> load
>> a carbon plugin and it crashes. I'm wondering wether this should be
>> case given the fact that the one and only reason for having such a
>> mechanism is to prevent this situation.
>
> Ideally, one shouldn't have this problem, but we might have to include
> this information. What does your crash log look like?
>
> -- Trenton



---
Axel Jäger
Developer

basysKom GmbH
Robert-Bosch-Str. 7 | 64293 Darmstadt | Germany
Tel: +49 6151 3969-961 | Fax: -736
axel.jaeger at basyskom.de | www.basyskom.de

Handelsregister: Darmstadt HRB 9352
Geschaeftsfuehrung: Eva Brucherseifer