http://bugs.winehq.org/show_bug.cgi?id=25961
Summary: Visual C++ 2008 runtime not marked as installed by
default
Product: Wine
Version: 1.3.12
Platform: x86
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: msvcrt
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
The installer for the app I'm looking at now
checks for the visual c++ 2008 runtime, and runs
D:\\Redistributable\\vcredist_x86_en.exe if it wasn't found.
Now, one of these days, Wine's builtin msvcr / msvcp is going to suffice
for this and most other apps, at which point Wine might want to set
the registry to indicate that vcrun2008 is already installed.
This might be in the distant future, depending on how many apps need
the other things that come with the runtime package, like mfc and a full
msvcp, that wine does not yet provide. So this bug will likely remain
open for a long time (if it's not closed for being too far ahead of its time).
For the record, this seems to be how the app is checking whether vcrun2008
is installed:
0024:Call msi.MsiQueryProductStateW(0033e2de
L"{9A25302D-30C0-39D9-BD6F-21E6EC160475}") ret=0040b9ad
0024:Call advapi32.RegOpenKeyW(80000002,0033d6c2
L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\Managed\\S-1-5-4\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968)
ret=7ef2cd5c
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c
0024:Call advapi32.RegOpenKeyW(80000001,0033d6c2
L"Software\\Microsoft\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968)
ret=7ef2cd5c
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c
0024:Call advapi32.RegOpenKeyW(80000002,0033d6c2
L"Software\\Classes\\Installer\\Products\\D20352A90C039D93DBF6126ECE614057",0033d968)
ret=7ef2cd5c
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2cd5c
0024:Call advapi32.RegOpenKeyW(80000002,0033d4ca
L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-4\\Products\\D20352A90C039D93DBF6126ECE614057\\InstallProperties",0033d964)
ret=7ef2b600
0024:Ret advapi32.RegOpenKeyW() retval=00000002 ret=7ef2b600
0024:Ret msi.MsiQueryProductStateW() retval=ffffffff ret=0040b9ad
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=31990
Bug #: 31990
Summary: Add ability to upload extra files along with test ext
Product: Wine-Testbot
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: titan.costa(a)gmail.com
Classification: Unclassified
That would be good to have the ability to upload extra files (avi files, dlls,
.drv, ...) to perform individual test (not part of the test suite).
Otherwise it requires to embed the file or use a self extracting exe which are
not very convenient.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=33126
Bug #: 33126
Summary: divided SysEx and coalesced midiOutLongMsg
Product: Wine
Version: 1.5.25
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winealsa.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
Classification: Unclassified
Johannes Kroll reported in wine-patches that the KORG Kontrol Editor software
hung after sending an ill-formed SysEx via winealsa's midiOutLongMsg.
http://www.winehq.org/pipermail/wine-patches/2013-January/121335.html
The MIDIHDR data is F0 ... F7 00 00 00 (125 bytes).
http://www.winehq.org/pipermail/wine-devel/2013-February/098852.html
He observed that no hang occurs when skipping the trailing 3 zero bytes. F7 is
the "End Of SysEx" (EOX) marker.
It is still unclear what happens. MIDI HW is expected to skip over bogus
bytes, thus the zero bytes should cause no harm. OTOH, ALSA might be getting
into trouble processing ill-formed messages, and we don't know if or how many
bytes ALSA actually sent out through the serial port.
In any case, midiOutLongMsg handling in Wine needs fixes.
- winealsa should extract the F0...F7 part and send that as a SysEx.
- More generally, midiOutLong is known to accept not only SysEx packets, but
also coalesced status messages. Some MIDI authors prefer to send e.g. chords
via one LongMsg rather than successive calls to midiOutShortMsg, arguing that
it's faster. Hence all Wine MIDI drivers need to decompose midiOutLongMsg into
packets consisting of status message, regular SysEx ... and possibly junk.
- All APIs (MS, ALSA, OSS, CA) acknowledge the existence of divided SysEx. As
a result, framing SysEx with F0 ... F7 is entirely under application control.
The current winealsa framing code is simply wrong.
- winecoreaudio always declared 3 bytes for short messages, even program
change.
I have written a sequence of patches to fix all of this. The only thing that
is unclear is how to encapsulate garbage data like the above 3 zero bytes or
real time messages with ALSA. What ALSA API function and what ALSA message
type to use? Heck, I'm not even sure winealsa.drv/midi.c:modData is ok to send
a 2-byte MTC quarter frame via snd_seq_ev_set_sysex instead of using a
primitive that sets the type SND_SEQ_EVENT_CLOCK/TICK.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46392
Bug ID: 46392
Summary: Commandos: Behind Enemy Walls is freezing while using
native quartz.dll
Product: Wine
Version: 4.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: gang65(a)poczta.onet.pl
Distribution: ---
Created attachment 63153
--> https://bugs.winehq.org/attachment.cgi?id=63153
Terminal logs with WINEDEBUG=+quartz+gstreamer+amstream
Commandos: Behind Enemy Walls is freezing while using native quartz.dll.
This is caused lack of support for 8 bit colour mode (it is using in Cinepak
codec):
https://multimedia.cx/mirror/cinepak.txt
It is also visible in the logs with fixme warning:
003c:trace:gstreamer:accept_caps_sink 0x7add5558 0x7be6aac8
003c:fixme:gstreamer:amt_from_gst_caps_video Unknown bpp 8
The cinepak gstreamer codec is already installed with command (Ubuntu 18.04):
sudo apt install gstreamer1.0-libav:i386
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43542
Bug ID: 43542
Summary: MikuMikuMoving errors when loading audio file
Product: Wine
Version: 2.14
Hardware: x86
URL: https://sites.google.com/site/mikumikumoving/MikuMikuM
oving_v1275.zip
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 58940
--> https://bugs.winehq.org/attachment.cgi?id=58940
Log of the crash
Using native dotnet40 and d3dx9.
When loading an audio file (.wav), the program crashes.
After installing natuve devenum and quartz it errors with
> Retrieving the COM class factory for component with CLSID {C1F400A4-3F08-11D3-9F0B-006008039E37} failed fue to the following error: 80040154 Exception from HRESULT 0x80040154 (REGDB_E_CLASSNOTREG).
but doesn't crash.
Possibly related to https://bugs.winehq.org/show_bug.cgi?id=43541
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39206
Bug ID: 39206
Summary: Lylian demo hangs after intro video
Product: Wine
Version: 1.7.50
Hardware: x86-64
URL: http://www.fileplanet.com/217922/210000/fileinfo/Lylia
n-Demo
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 00cpxxx(a)gmail.com
Distribution: ---
Currently wine plays the introduction video but after that it hangs and only
resumes when a few keystrokes and/or mouse clicks are performed.
The problem seems related to quartz but since I'm not sure the component is not
set yet. The video playback ends but it looks like quartz does not recognize
that and keeps waiting for things to happen.
Last lines from the quartz log:
0032:trace:quartz:StdMediaSample2_Release (0x1bb4c0)->(): new ref = 0
0032:trace:quartz:BaseMemAllocator_ReleaseBuffer (0x1baea0)->(0x1bb4c0)
0032:trace:quartz:StdMediaSample2_Release (0x1b92a8)->(): new ref = 0
0032:trace:quartz:BaseMemAllocator_ReleaseBuffer (0x1b8298)->(0x1b92a8)
0032:trace:quartz:AVISplitter_SendEndOfFile End of file reached
0032:fixme:qedit:SampleGrabber_IPin_EndOfStream : stub
0032:trace:quartz:AVISplitter_SendEndOfFile --> 0
0032:trace:quartz:AVISplitter_thread_reader Thread 0 terminated properly
002e:fixme:quartz:FileAsyncReader_WaitForNext Returned: 258 (00000578)
002e:trace:quartz:FileAsyncReader_WaitForNext -- 8004022e
002e:trace:quartz:PullPin_Thread_Process Process sample
002e:trace:quartz:FileAsyncReader_WaitForNext (10000, 0x139e924, 0x139e910)
002e:warn:quartz:FileAsyncReader_WaitForNext Called without samples in queue
and not flushing!!
002e:fixme:quartz:FileAsyncReader_WaitForNext Returned: 258 (00000578)
002e:trace:quartz:FileAsyncReader_WaitForNext -- 8004022e
002e:trace:quartz:PullPin_Thread_Process Process sample
002e:trace:quartz:FileAsyncReader_WaitForNext (10000, 0x139e924, 0x139e910)
002e:warn:quartz:FileAsyncReader_WaitForNext Called without samples in queue
and not flushing!!
002e:fixme:quartz:FileAsyncReader_WaitForNext Returned: 258 (00000578)
002e:trace:quartz:FileAsyncReader_WaitForNext -- 8004022e
The last 4 lines repeat forever.
If I change the game AVI file to any other AVI it plays fine and ends fine.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=35163
Bug ID: 35163
Summary: Victoria 2 crashes on start with built-in quartz
Product: Wine
Version: 1.7.8
Hardware: x86
URL: http://www.gamershell.com/download_85888.shtml
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 46906
--> http://bugs.winehq.org/attachment.cgi?id=46906
terminal output
The game crashes shortly after starting with Wine's built-in quartz.dll.
'winetricks quartz' is a workaround.
Lots of
>fixme:quartz:parse_header Not a valid header: ff:ff:ff:ff
are preceding the crash. They're probably the game music files (mp3 format)
that causing the problem.
Fedora 19
wine-1.7.8-114-g1928d61 (compiled from source without gstreamer support)
Alsa 1.0.27 (Pulseaudio is not running)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45810
Bug ID: 45810
Summary: WINEPATH maximums
Product: Wine
Version: 3.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: paleozogt(a)gmail.com
Distribution: ---
Created attachment 62272
--> https://bugs.winehq.org/attachment.cgi?id=62272
winepath-test.sh
WINEPATH seems to have some undocumented limits, which cause the in-windows
PATH to be corrupted.
One limit, around 969 characters, causes the PATH to drop the suffix that's
usually appended (C:\windows\system32;C:\windows;C:\windows\system32\wbem).
Another limit, around 1025 characters, causes the PATH to entirely ignore
what's in WINEPATH.
I'm not sure why these limits exist-- can't Windows support arbitrarily long
PATHs? (I've routinely seen huge PATHs on Win7/Win10.)
The attached winepath-test.sh makes a WINEPATH of various sizes and then echos
the size and the %PATH% in the cmd shell.
The output looks like:
> $ ./winepath-test.sh
>
> 968
> C:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa;C:\windows\system32;C:\windows;C:\windows\system32\wb
>
> 969
> C:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>
> 1024
> C:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
>
> 1025
> C:\windows\system32;C:\windows;C:\windows\system32\wbem
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44888
Bug ID: 44888
Summary: Wrong texture in Assassin's Creed : Revelations
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
CC: matteo.mystral(a)gmail.com
Distribution: ---
Created attachment 60959
--> https://bugs.winehq.org/attachment.cgi?id=60959
Good Texture before to use Eagle Vision
Hi,
In game, when you use the "Eagle Vision", there are graphical glitches each
time you disable it to return to the "Normal Vision". I took 2 screenshots
because it's better than words.
I tried everything, set d3dx9_* to native, enable/disable cmst. I have this
issue with Mesa-Git and Mesa 17.3.7.
SYSTEM :
- Gentoo amd64
- AMD Rx 560 - 4Go
- Mesa git / Mesa 17.3.7 + LLVM 5.0.1
- Wine-Staging 3.5 -> Need it, because Uplay doesn't work without it.
I have a lot of these warning/error when i launch the game :
[...]
00e7:fixme:d3d:surface_convert_format Cannot find a conversion function from
format WINED3DFMT_B8G8R8X8_UNORM to WINED3DFMT_L8_UNORM.
00e7:fixme:d3d:surface_cpu_blt Cannot convert WINED3DFMT_B8G8R8X8_UNORM to
WINED3DFMT_L8_UNORM.
00e7:err:d3d:cpu_blitter_blit Failed to blit.
[...]
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=21344
Summary: Buffer overflow in WCMD_run_program
Product: Wine
Version: 1.1.36
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dima(a)gmail.com
The WCMD_run_program function in wcmdmain.c copies pathposn into thisDir
without checking the size:
/* Work on the first directory on the search path */
pos = strchrW(pathposn, ';');
if (pos) {
memcpy(thisDir, pathposn, (pos-pathposn) * sizeof(WCHAR));
thisDir[(pos-pathposn)] = 0x00;
pathposn = pos+1;
} else {
strcpyW(thisDir, pathposn);
pathposn = NULL;
}
The size of pathposn can be up to MAXSTRING, while thisDir has size MAX_PATH.
To reproduce:
$ wine cmd /c
'Z:\xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\foo'
err:seh:setup_exception_record stack overflow 2144 bytes in thread 0019 eip
7bc3ea3e esp 00230ad0 stack 0x230000-0x231000-0x330000
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.