January 2004 - Wine-bugs - list.winehq.org

[Bug 1946] New: build from CVS fails on Mandrake 9.2 - broken pipe / bison / flex (Mandrake 9.2 linux 2.4.22-10mdk)
by Wine Bugs 18 Jan '04

18 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1946 Summary: build from CVS fails on Mandrake 9.2 - broken pipe / bison / flex (Mandrake 9.2 linux 2.4.22-10mdk) Product: Wine Version: CVS Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-misc AssignedTo: wine-bugs(a)winehq.org ReportedBy: zippy(a)cs.brandeis.edu I downloaded the most recent version of Winex from CVS (also tried the 3.2.1 tag, same results). The files all seem to be there, but the configuration script fails with an error about a broken pipe. The build chugs along for quite a while and then ends with: cd `dirname wmc/__depend__` && make depend make[2]: Entering directory `/home/patrick/winex/winex/tools/wmc' ../../tools/makedep -I. -I. -I../../include -I../../include -C. lang.c mcl.c utils.c wmc.c write.c mcy.y -C. make[2]: Leaving directory `/home/patrick/winex/winex/tools/wmc' cd `dirname wrc/__depend__` && make depend make[2]: Entering directory `/home/patrick/winex/winex/tools/wrc' bison -y -bppy -ppp -d -t ./ppy.y make[2]: *** [ppy.tab.c] Broken pipe make[2]: Leaving directory `/home/patrick/winex/winex/tools/wrc' make[1]: *** [wrc/__depend__] Error 2 make[1]: Leaving directory `/home/patrick/winex/winex/tools' make: *** [tools/__depend__] Error 2 Compilation failed, aborting install. [patrick(a)localhost winex]$ --- I get a slightly different result running the build manually using "make && make depend". Again, the build runs for a while and then: gcc -g -O2 -Wall -mpreferred-stack-boundary=2 -fno-keep-static-consts -D__const=const -D__int8=char -D__int16=short -D__int32=int "-D__int64=long long" -o winedump debug.o main.o misc.o msmangle.o output.o pe.o search.o symbol.o make[2]: Leaving directory `/home/patrick/winex/winex/tools/winedump' make[2]: Entering directory `/home/patrick/winex/winex/tools/wmc' gcc -c -I. -I. -I../../include -I../../include -g -O2 -Wall -mpreferred-stack-boundary=2 -fno-keep-static-consts -D__const=const -D__int8=char -D__int16=short -D__int32=int "-D__int64=long long" -D__WINE__ -D_REENTRANT -I/usr/X11R6/include -o lang.o lang.c bison -y -d -t ./mcy.y make[2]: *** [y.tab.h] Broken pipe make[2]: Leaving directory `/home/patrick/winex/winex/tools/wmc' make[1]: *** [wmc] Error 2 make[1]: Leaving directory `/home/patrick/winex/winex/tools' make: *** [tools] Error 2 [patrick(a)localhost winex]$ --- [patrick(a)localhost winex]$ uname -a Linux localhost 2.4.22-10mdk #1 Thu Sep 18 12:30:58 CEST 2003 i686 unknown unknown GNU/Linux [patrick(a)localhost winex]$ bison --version bison (GNU Bison) 1.875 [patrick(a)localhost winex]$ flex --version flex version 2.5.4 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

Re: [Bug 1944] RtlpWaitForCriticalSection wait timed out in thread
by jau＠iki.fi 18 Jan '04

18 Jan '04

Quoting Wine Bugs: > > http://bugs.winehq.org/show_bug.cgi?id=1944 > > > > > > ------- Additional Comments From marcus(a)jet.franken.de 2004-17-01 19:20 ------- > how old is your system? FreeBSD-4.9-STABLE -- system updated at least once a week from the latest cvsup sources. So, you can count it as being practically always the latest and greatest 4.9. > what is your XFree86 version? Otherwise 4.3.0, but the server is snap 4.3.99.15. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Mawit Ltd, Finland /__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Mawit.Com (Home) +358-9-6215-280 / Internet: ukkonen(a)nic.funet.fi v Internet: jau(a)iki.fi + + + + My opinions are mine and mine alone, not my employers. + + + +

1 0

[Bug 1945] New: MYOB v11, strange dialog box on load, crashes after short period of time
by Wine Bugs 18 Jan '04

18 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1945 Summary: MYOB v11, strange dialog box on load, crashes after short period of time Product: Wine Version: 20031212 Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.org ReportedBy: derek(a)dereksplace.co.nz MYOB version 12 (from www.myob.co.nz) displays dialog box (sic) "FALT is needs that bit cleared. [OK]" Click [OK], dialog appears 36 times before MYOB starts. Seems to run okay for about 2-3 minutes before hanging. Each time initial dialog is clicked, console log shows: fixme:accel:CreateAcceleratorTableA should check that the accelerator descriptions are valid, return NULL and SetLastError() if not. When trying to open it's data file (standard Windows File Open dialog appears) console log shows: fixme:commdlg:GetFileName95 Flags 0x00002000 not yet implemented err:dosfs:DRIVE_ReadSuperblock Couldn't open device '' for drive F: ! (not available or symlink not valid ?) err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it or make sure the device to read it from is accessible ! err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on (F:). fixme:dosfs:DRIVE_GetSerialNumber Serial number reading from file system on drive F: not supported yet. During program execution, this message appears numerous (40+) times, whenever the mouse pointer hovers over a link or button in the MYOB gui: fixme:font:SetMapperFlags (0x730, 0x00000000): stub - harmless After a period of time (2-3 minutes) or after opening a few child windows, MYOB hangs. Console shows: fixme:msvcrt:_XcptFilter (-1073741819,0x406cf63c)semi-stub wine: Unhandled exception (thread 001f), starting debugger... WineDbg starting on pid 1e Loaded debug information from ELF 'wine' ((nil)) No debug information in 32bit DLL 'C:\myob12\Myob.exe' (0x400000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x40200000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40490000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x40a50000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x408a0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40720000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\IPHLPAPI.DLL' (0x40aa0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WS2_32.DLL' (0x40ac0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NETAPI32.DLL' (0x40a80000) No debug information in 32bit DLL 'C:\MYOB12\CTMYOB32.DLL' (0x10000000) No debug information in 32bit DLL 'C:\MYOB12\MYOBSP32.DLL' (0x406d0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40c40000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40bc0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x40c90000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40ce0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x40b30000) No debug information in 32bit DLL 'C:\MYOB12\CPDF.DLL' (0x40add000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' (0x40d90000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x40dc0000) No debug information in 32bit DLL 'C:\MYOB12\XERCES.DLL' (0x12000000) No debug information in 32bit DLL 'C:\MYOB12\MFC42.DLL' (0x73dd0000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINSPOOL.DRV' (0x40e80000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMDLG32.DLL' (0x40e00000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40f60000) No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x43290000) No debug information in 32bit DLL 'C:\MYOB12\CFX2032.DLL' (0x4322d000) Unhandled exception: page fault on read access to 0x40430000 in 32-bit code (0x4010574c). In 32-bit mode. 0x4010574c (NTDLL.DLL.memcpy+0x1c): repe movsl (%esi),%es:(%edi) Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>syntax error Wine-dbg>syntax error Wine-dbg>syntax error Wine-dbg>syntax error The last line repeats for quite some time, sometimes the only way to get out of it is to kill the terminal session. If Ctrl-C is pressed in the debugger (if it stops prompting) then this message appears: err:seh:setup_exception nested exception on signal stack in thread 001f eip 400466c6 esp 40016bac stack 0x405d0000-0x406d0000 But more often than not even if debugger is stopped and control is returned to the bash prompt the last line starts scrolling all over the screen (no line feed beterrn messages) and the terminal must then be killed. Application Details: MYOB version 12 (New Zealand Customised version) from http://www.myob.co.nz) Running on Mandrake 9.2 Linux 2.4.22-10mdk Wine 20031212 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1944] RtlpWaitForCriticalSection wait timed out in thread
by Wine Bugs 18 Jan '04

18 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1944 ------- Additional Comments From marcus(a)jet.franken.de 2004-17-01 19:20 ------- how old is your system? what is your XFree86 version? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1894] Segmentation Faults when running wine [ exec-shield BSS hack fails on machines without overcommit switched on ]
by Wine Bugs 18 Jan '04

18 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1894 marcus(a)jet.franken.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbrown106(a)swift-mail.com ------- Additional Comments From marcus(a)jet.franken.de 2004-17-01 19:19 ------- *** Bug 1942 has been marked as a duplicate of this bug. *** -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 1942] wine segfaults immediately upon launch
by Wine Bugs 18 Jan '04

18 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1942 marcus(a)jet.franken.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From marcus(a)jet.franken.de 2004-17-01 19:19 ------- same bug as 1894. the problem is wine has a 256MB static array (you don't see it in the binary, it is just a marked section), which the linker wants to check is there. However, allocation it fails, sinc the kernel doesnot have that much memory and does not want to overcommit memory. this is a workaround for other stuff in Redhat 9/Fedora Core 1... not solved yet *** This bug has been marked as a duplicate of 1894 *** -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1944] New: RtlpWaitForCriticalSection wait timed out in thread
by Wine Bugs 17 Jan '04

17 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1944 Summary: RtlpWaitForCriticalSection wait timed out in thread Product: Wine Version: 20031212 Platform: Other OS/Version: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-binary AssignedTo: wine-bugs(a)winehq.org ReportedBy: jau(a)iki.fi I tried to install the game Pharaoh to test how well wine manages. When the installation automate was running I got these error message... err:ntdll:RtlpWaitForCriticalSection section 0x20777520 "../../windows/user.c: USER_SysLevel" wait timed out in thread 000c, blocked by 000b, retrying (60 sec) winewine in free(): warning: recursive call wine in malloc(): warning: recursive call in malloc(): warning: recursive call err:ntdll:RtlpWaitForCriticalSection section 0x20947120 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 000b, blocked by 000c, retrying (60 sec) wine: Unhandled exception (thread 000b), starting debugger... after this wine gave up. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1943] InvalidateRect( hDeskTopWindow,0,0) does not work
by Wine Bugs 17 Jan '04

17 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1943 ------- Additional Comments From eetasoft(a)online.ee 2004-17-01 15:20 ------- Created an attachment (id=492) --> (http://bugs.winehq.org/attachment.cgi?id=492&action=view) executable and vfp source to reproduce bug 1943 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1943] New: InvalidateRect( hDeskTopWindow,0,0) does not work
by Wine Bugs 17 Jan '04

17 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1943 Summary: InvalidateRect( hDeskTopWindow,0,0) does not work Product: Wine Version: 20031212 Platform: PC OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gdi AssignedTo: wine-bugs(a)winehq.org ReportedBy: eetasoft(a)online.ee To reproduce: 1. unzip bug attachment files to some directory. 2. Add the following lines to WINE config file: [Version] "Windows" = "nt351" 3. Run WINE invalidaterectbug.exe 4. Press down arrow key ten times or scroll down 5. Press up arrow ten times or scroll up Observed result: A garbage foxpro report preview screen appears and remains. Expected result: A garbage screen must disapper after each 1 second. This code calls InvalidateRect(hGetDeskTopWindow,0,0) after each second. InvalidateRect() must forse correct repainting of screen. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

[Bug 1942] wine segfaults immediately upon launch
by Wine Bugs 17 Jan '04

17 Jan '04

http://bugs.winehq.org/show_bug.cgi?id=1942 ------- Additional Comments From jbrown106(a)swift-mail.com 2004-17-01 12:47 ------- Turning on overcommit_memory makes wine work without a hitch. Someone should put this in the README file. One question though. Why does it segfault when overcommit is off? Is this still considered a bug, or is it just something that we're gonna live with? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0