Le 05/02/2013 16:02, Thiago Macieira a écrit : > On terça-feira, 5 de fevereiro de 2013 09.34.54, Yves Bailly wrote: >> A segmentation fault... stack trace: >> >> 0 load<int> qgenericatomic.h 98 0x40d87f >> 1 QBasicAtomicInteger<int>::load qbasicatomic.h 145 0x40d87f >> 2 QtPrivate::RefCount::isShared qrefcount.h 99 0x40d973 >> 3 QVector<char*>::isDetached qvector.h 109 0x40d905 >> 4 QVector<char*>::detach qvector.h 306 0x40d464 >> 5 QVector<char*>::data qvector.h 128 0x40d437 >> 6 WinMain@16 qtmain_win.cpp 131 0x4026ee >> 7 main main.c 73 0x40244e > > Crash inside qtmain. It's probably the same as this already-filed bug report: > https://bugreports.qt-project.org/browse/QTBUG-29443
Looks similar, however the crash is inside qgenericatomic.h, not qtmain. > The reporter there provided a patch which looks completely unrelated to the > problem at hand. If indeed it is solving a problem, then we must conclude that > the problem is a miscompilation. If that's the case, the solution is: shoot > the compiler in the head. I used the provided pre-build binaries, I did not compile Qt myself. Installer used: http://releases.qt-project.org/qt5/5.0.1/qt-windows-opensource-5.0.1-mingw47_32-x86-offline.exe So I don't really know who should shoot which compiler in the head... ;-) Anyway this is getting really frustrating, since the 5.0 initial release I can't get a Qt working even remotely correctly on my Win7/64bits computer... even this 32bits, MinGW-compiled release doesn't work properly, even using the provided pre-build binaries. I'm ready to try and check whatever one might ask, I just don't have an idea where to start. Regards, -- /- Yves Bailly - Software developer -\ \- Sescoi R&D - http://www.sescoi.fr -/ "The possible is done. The impossible is being done. For miracles, thanks to allow a little delay." _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
