Qt-interest Archive, March 2007
new mac proc crashing after execve
Message 1 in thread
I have an app running on a mac in a regular app bundle that uses
execve to start my qt app, which is also in an app bundle. The problem
is that the qt app bundle crashes here:
0 com.apple.CoreFoundation 0x90834a3a CFBundleCopyExecutableURL + 11
1 QtCore 0x052ba7ff qAppFileName() + 129
2 QtCore 0x052a3539
QCoreApplication::applicationFilePath() + 71
3 QtCore 0x052a3e1d
QCoreApplicationPrivate::appendApplicationPathToLibraryPaths() + 33
4 QtCore 0x052a4090
QCoreApplication::libraryPaths() + 314
5 QtCore 0x052a4456 QCoreApplication::init() + 178
6 QtCore 0x052a463f
QCoreApplication::QCoreApplication[not-in-charge](QCoreApplicationPrivate&)
+ 59
7 QtGui 0x04a14a07
QApplication::QApplication[not-in-charge](int&, char**, int) + 73
Some guys on #macdev said that's because the second app bundle still
thinks it is the first app bundle, so the CFBundle calls fail, which
qt is unprepared for.
Bottom line: The first app is one of many the starts the second (qt)
app with particular command line arguments, kind of like a glorified
shortcut. What is the correct way to do this without the qt app
crashing?
--
[ signature omitted ]
