[Development] [Announce] Qt 5.0.1 released

[Koehne Kai]

> -----Original Message-----
> From: development-bounces+kai.koehne=digia.com at qt-project.org
> [mailto:development-bounces+kai.koehne=digia.com at qt-project.org] On
> Behalf Of Yves Bailly
> Sent: Tuesday, February 05, 2013 8:40 AM
> To: development at qt-project.org
> Subject: Re: [Development] [Announce] Qt 5.0.1 released
> 
> Greetings all,
> 
> Le 31/01/2013 14:10, List for announcements regarding Qt releases and
> development a écrit :
> > I'm happy to announce that Qt 5.0.1 is now released.
> >
> > See the blog on
> > http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/
> 
> I've just downloaded and insalled the (huge) bundle "Qt 5.0.1 for Windows
> 32-bit" with included MinGW 4.7. Installed fine on a 64bits, Win7 host.
> 
> QtCreator starts fine, but...
> 
> The "analogclock" example doesn't start. Even if I try to create an almost-
> empty project (you know, the default, auto-generated one with a single
> QMainWindow), it doesn't start either - debug or release.
> 
> Profiling using DependencyWalker ends with this:
> 
> [...many messages...]
> 00:00:09.298: DllMain(0x10220000, DLL_PROCESS_ATTACH, 0x0028FD24) in
> "c:\qt501\5.0.1\mingw47_32\bin\QT5WIDGETSD.DLL" called by thread 1.
> 00:00:09.298: DllMain(0x10220000, DLL_PROCESS_ATTACH, 0x0028FD24) in
> "c:\qt501\5.0.1\mingw47_32\bin\QT5WIDGETSD.DLL" returned 1 (0x1) by
> thread 1.
> 00:00:09.298: GetProcAddress(0x75500000
> [c:\windows\syswow64\MSVCRT.DLL], "_get_output_format") called from
> "c:\qt501\5.0.1\mingw47_32\bin\ICUUC49.DLL" at address 0x675F3009 and
> returned 0x75575CE8 by thread 1.
> 00:00:09.298: First chance exception 0xC0000005 (Access Violation) occurred
> in "c:\qt501\5.0.1\mingw47_32\examples\widgets\widgets\analogclock-
> build-desktop_qt_5_0_1_mingw_32bit-debug\debug\ANALOGCLOCK.EXE"
> at address 0x0040D87F by thread 1.
> 00:00:09.313: Second chance exception 0xC0000005 (Access Violation)
> occurred in
> "c:\qt501\5.0.1\mingw47_32\examples\widgets\widgets\analogclock-build-
> desktop_qt_5_0_1_mingw_32bit-debug\debug\ANALOGCLOCK.EXE"
> at address 0x0040D87F by thread 1.
> 00:00:09.313: Exited
> "c:\qt501\5.0.1\mingw47_32\examples\widgets\widgets\analogclock-build-
> desktop_qt_5_0_1_mingw_32bit-debug\debug\ANALOGCLOCK.EXE"
> (process 0x1064) with code -1073741819 (0xC0000005) by thread 1.

That's weird. For the record that's my log after _get_output_format call (also with Win7/64 bit) ...

00:00:11.781: GetProcAddress(0x766F0000 [c:\windows\syswow64\MSVCRT.DLL], "_get_output_format") called from "c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\bin\ICUUC49.DLL" at address 0x675F3009 and returned 0x76765CE8.
00:00:11.797: LoadLibraryExW("C:\Qt\Qt5.0.1-mingw\5.0.1\mingw47_32\plugins\platforms\qminimal.dll", 0x00000000, DONT_RESOLVE_DLL_REFERENCES) called from "c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\bin\QT5CORED.DLL" at address 0x6B941EE9.
00:00:11.812: Loaded "c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\plugins\platforms\QMINIMAL.DLL" at address 0x67D40000.  Successfully hooked module.
00:00:11.812: LoadLibraryExW("C:\Qt\Qt5.0.1-mingw\5.0.1\mingw47_32\plugins\platforms\qminimal.dll", 0x00000000, DONT_RESOLVE_DLL_REFERENCES) returned 0x67D40000.
00:00:11.843: GetProcAddress(0x67D40000 [c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\plugins\platforms\QMINIMAL.DLL], "qt_plugin_query_metadata") called from "c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\bin\QT5CORED.DLL" at address 0x6B941F4D and returned 0x67D41680.
00:00:11.843: Unloaded "c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\plugins\platforms\QMINIMAL.DLL" at address 0x67D40000.
00:00:11.843: LoadLibraryExW("C:\Qt\Qt5.0.1-mingw\5.0.1\mingw47_32\plugins\platforms\qminimald.dll", 0x00000000, DONT_RESOLVE_DLL_REFERENCES) called from "c:\qt\qt5.0.1-mingw\5.0.1\mingw47_32\bin\QT5CORED.DLL" at address 0x6B941EE9.
....

Don't know whether the problem is indeed in the icu (or handling of its results in Qt5Core), or if for some reason the loading of platform plugins fails. Doesn't the debugger show you anything? 

> 
> Starting other Qt programs, such as "designer" or "linguist" from the
> provided command-line works fine.
> Any hint or idea? I really don't know where to investigate here...

Did you try to launch the example from exactly the same environment/command line as designer or linguist?

Regards

Kai

PS: Could you create a bug in the bugtracker, and fill in the details there? It's just easier to track there ...

 
> Thanks in advance.
> 
> --
>       /- 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 at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development