PDA

View Full Version : All binaries in 4.6.1 crash on OSX 10.5



Markus
10th February 2010, 19:33
Dear all,

I am using qt-everywhere-commercial-src-4.6.1 and compile works fine. Also my own projects all compile and run fine but non of the Qt apps in /bin or /examples run. Below is the crash dump on qtdemos.

Any idea whats wrong?

Markus



Process: qtdemo [6449]
Path: /usr/local/Trolltech/Qt-4.6.1/bin/qtdemo.app/Contents/MacOS/qtdemo
Identifier: com.trolltech.qt.demo
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [115]

Interval Since Last Report: 200 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 3 sec
Per-App Crashes Since Last Report: 1

Date/Time: 2010-02-10 11:28:26.141 -0800
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: 9C2E08A1-4986-4783-BAE7-03EA07FEE18C

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 libSystem.B.dylib 0x00007fff812fef16 __kill + 10
1 com.trolltech.qt.demo 0x000000010093f275 qt_message_output(QtMsgType, char const*) + 133
2 com.trolltech.qt.demo 0x000000010093f417 qt_message(QtMsgType, char const*, __va_list_tag*) + 183
3 com.trolltech.qt.demo 0x000000010093f60a qFatal(char const*, ...) + 170
4 com.trolltech.qt.demo 0x00000001001b1d31 qt_init(QApplicationPrivate*, int) + 1937
5 com.trolltech.qt.demo 0x000000010021d094 QApplicationPrivate::construct() + 68
6 com.trolltech.qt.demo 0x000000010021d4f6 QApplication::QApplication(int&, char**, int) + 102
7 com.trolltech.qt.demo 0x00000001000052d9 main + 57
8 com.trolltech.qt.demo 0x0000000100005274 start + 52

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x00007fff5fbff648 rdx: 0x0000000000000000
rdi: 0x0000000000001931 rsi: 0x0000000000000006 rbp: 0x00007fff5fbff660 rsp: 0x00007fff5fbff648
r8: 0x00007fffffe00838 r9: 0x00000001012ed538 r10: 0x00007fff812d6e36 r11: 0x0000000000000202
r12: 0x0000000000000003 r13: 0x00007fff5fbff710 r14: 0x0000000000000003 r15: 0x00007fff5fbff880
rip: 0x00007fff812fef16 rfl: 0x0000000000000202 cr2: 0x00007fff70128950

axeljaeger
12th February 2010, 10:31
Use Console.app to get the message that was send by the qapplcation. Your backtrace shows that the application crashes in the Qt message handler. This is intended behavior if someone puts out a message using qFatal. Not the actual text message would be interesting. It is given on the command line: Either start your application binary from the command line, e.g. the executable inside the bundle structure or use console.app to get the command line output of all applications that are launched via the finder GUI.

Markus
12th February 2010, 17:29
I have the console printout:

Qt internal error: qt_menu.nib could not be loaded. The .nib file should be placed in QtGui.framework/Versions/Current/Resources/ or in the resources directory of your application bundle.
Abort

axeljaeger
12th February 2010, 20:42
Can you find that file in either location?

Markus
13th February 2010, 00:48
I cannot find any .nib files in Qt at all.
Even in qt-sdk-mac-commercial-2010.01.dmg apps -- which do not crash -- are no nib files.

axeljaeger
14th February 2010, 16:58
Then this SDK is probably linking against carbon.

Markus
17th February 2010, 00:29
I got answer from the support and my problem is the following:

I am using the -static and x86_64 flags for the configure of the Qt build. This combination does not work because of Cocoa.

All my fault...