Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Update mingw32-runtime to 3.18
https://bugzilla.redhat.com/show_bug.cgi?id=629209
Summary: Update mingw32-runtime to 3.18
Product: Fedora
Version: 14
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mingw32-runtime
AssignedTo: rjones(a)redhat.com
ReportedBy: atkac(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: rjones(a)redhat.com, kalev(a)smartlink.ee,
fedora-mingw(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Description of problem:
When I compile TigerVNC vncviewer for Windows on Fedora 14/rawhide, output
vncviewer.exe binary is broken:
...
Backtrace:
=>0 0x00485e4f in vncviewer (+0x85e4f) (0x00a0fe30)
1 0x0040108d __mingw_CRTStartup+0x6c()
[/builddir/build/BUILD/mingwrt-3.15.2-mingw32/crt1.c:217] in vncviewer
(0x00a0fe70)
2 0x0040108d __mingw_CRTStartup+0x6c()
[/builddir/build/BUILD/mingwrt-3.15.2-mingw32/crt1.c:217] in vncviewer
(0x00a0fe90)
3 0x00401128 WinMainCRTStartup+0x17()
[/builddir/build/BUILD/mingwrt-3.15.2-mingw32/crt1.c:271] in vncviewer
(0x00a0fea8)
4 0x7ede70bc call_process_entry+0xb() in kernel32 (0x00a0fee8)
5 0x7efab570 call_thread_func+0xb() in ntdll (0x00a0fef8)
6 0x7efae1f1 call_thread_entry_point+0x70() in ntdll (0x00a0ffc8)
7 0x7ef83feb call_dll_entry_point+0x65a() in ntdll (0x00a0ffe8)
...
When I updated to the latest mingw runtime from upstream
(mingwrt-3.18-mingw32-src) everything works fine.
Version-Release number of selected component (if applicable):
mingw32-runtime-3.15.2-5.fc13
How reproducible:
always
Steps to Reproduce:
1. compile program for Windows via MinGW build chain
2. run it
Actual results:
crash
Expected results:
working binary
Additional info:
It seems current mingw runtime is not compatible with gcc 4.5. As I wrote above
when I update to 3.18 version, problem disappears.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.