Hi,
On Thu, Jan 24, 2013 at 7:08 AM, Joshua Grauman <jnf...@grauman.com> wrote:
> First a disclaimer, I know very little about Mac OS specifics. I only have
> a Mac to build my app for it.
>
> I am porting two apps to Mac OS Mountain Lion and Qt5. The apps have run
> fine on quite a few of the Qt4 series versions in Windows/Linux/Mac (Snow
> Leopard). They both run fine in Qt5/Linux. I just installed the latest
> Mountain Lion version with latest XCode. I've gotten them to compile by
> running:
>
> qmake -spec macx-xcode project.pro
> xcodebuild
>
> But two completely different programs both segfault on a simple line:
>
> QFile file("file");
> if(!file.open(QIODevice::ReadOnly | QIODevice::Text))
> exit(0);
> QTextStream in(&file);
> in.setCodec("UTF-8");
> while(!in.atEnd())
> {
> QString line = in.readLine(); //segfault here
> ...
>
> At first I thought it was new Mac OS sandboxing stupidity limiting my file
> acces, but I have have been able to get that line to run fine in a minimal
> example (so I'm guessing that's not it, but I'm still not positive).
Where's your backtrace? A backtrace should be able to tell you at
least where exactly it segfaults (possibly within Qt code). And make
sure you have Qt built with debugging symbols, otherwise the backtrace
won't be very useful.
Andreas
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
