November 2003 - Wine-Devel - list.winehq.org

Freeze in Agent 2.0 beta.
by Rein Klazes Nov. 18, 2003

Nov. 18, 2003

Hi, When downloading headers form multiple groups Agent often locks up. The program does the following: -(Main). main thread creates a sub thread: | 0009:Call kernel32.CreateThread(00000000,00002000,006648e0,41ac6cb0,00000004,41ac6cb0) ret=006649c9 | 0009: *fd* 23 <- 41 | 0009: new_thread( suspend=1, inherit=0, request_fd=23 ) | 0009: new_thread() = 0 { tid=0021, handle=0xcc } | 0021: *fd* 27 <- 42 | 0021: *fd* 29 <- 45 | 0021: init_thread( unix_pid=4966, unix_tid=-1, teb=0x40319000, entry=0x404fa110, reply_fd=27, wait_fd=29 ) | 0021: init_thread() = 0 { pid=0008, tid=0021, boot=0, version=126 } | 0021: select( flags=8, cookie=0x4031ac78, timeout=1068729666.690492 (-0.000050), handles={} ) | 0021: select() = PENDING | 0009:Ret kernel32.CreateThread() retval=000000cc ret=006649c9 -(SUB). Sub thread updates some files and finishes with sending a WM_NULL message to the main thrad: | 0021:Call user32.PostMessageA(00010026,00000000,00000000,00000000) ret=0058d0d6 | 0021:Call kernel32.GetTickCount() ret=407924ca | 0021:Ret kernel32.GetTickCount() retval=000ab0db ret=407924ca | 0021: send_message( id=0009, type=6, flags=0, win=0x10026, msg=00000000, wparam=00000000, lparam=00000000, x=0, y=0, time=000ab0db, info=00000000, timeout=-1, callback=(nil), data={} ) | 0021: send_message() = 0 | 0021:Ret user32.PostMessageA() retval=00000001 ret=0058d0d6 -(SUB). Close the thread handle: | 0021:Call kernel32.CloseHandle(000000cc) ret=006648d0 | 0021: close_handle( handle=0xcc ) | 0021: close_handle() = 0 { fd=-1 } | 0021:Ret kernel32.CloseHandle() retval=00000001 ret=006648d0 -(SUB). terminates: | 0021:Call kernel32.ExitThread(00000000) ret=006648df | 0021: terminate_thread( handle=0xfffffffe, exit_code=0 ) | 0021: terminate_thread() = 0 { self=1, last=0 } [snip] | 0021:Ret PE DLL (proc=0x4079ad40,module=0x406f0000 L"user32.dll",reason=THREAD_DETACH,res=(nil)) retval=1 | 0021:Call PE DLL (proc=0x40cef0a0,module=0x40cb0000 L"x11drv.dll",reason=THREAD_DETACH,res=(nil)) | 0021:Ret PE DLL (proc=0x40cef0a0,module=0x40cb0000 L"x11drv.dll",reason=THREAD_DETACH,res=(nil)) retval=1 | 0021:Call PE DLL (proc=0x404c8980,module=0x40480000 L"kernel32.dll",reason=THREAD_DETACH,res=(nil)) | 0021:Ret PE DLL (proc=0x404c8980,module=0x40480000 L"kernel32.dll",reason=THREAD_DETACH,res=(nil)) retval=1 | 0021: *killed* exit_code=0 -(Main). In the meantime the main thread: - gets data from the server (winsok send and rcv) - writes to the file - processes queued messages until it is empty - then is wait on the handle of the subthread: | 0009:Call kernel32.WaitForSingleObject(000000cc,ffffffff) ret=004ed693 -(Main). which ends immedeately: | 0009: select( flags=4, cookie=0x406cf4e0, timeout=0, handles={0xcc} ) | 0009: select() = INVALID_HANDLE | 0009:Ret kernel32.WaitForSingleObject() retval=ffffffff ret=004ed693 -(Main). close the subthread handle. | 0009:Call kernel32.CloseHandle(000000cc) ret=004ed69c | 0009: close_handle( handle=0xcc ) | 0009: close_handle() = INVALID_HANDLE { fd=0 } | 0009:Ret kernel32.CloseHandle() retval=00000000 ret=004ed69c This may repeat a number of times but then without warning: -(SUB). terminates as usual: | 0023:Ret PE DLL (proc=0x4079ad40,module=0x406f0000 L"user32.dll",reason=THREAD_DETACH,res=(nil)) retval=1 | 0023:Call PE DLL (proc=0x40cef0a0,module=0x40cb0000 L"x11drv.dll",reason=THREAD_DETACH,res=(nil)) | 0023:Ret PE DLL (proc=0x40cef0a0,module=0x40cb0000 L"x11drv.dll",reason=THREAD_DETACH,res=(nil)) retval=1 | 0023:Call PE DLL (proc=0x404c8980,module=0x40480000 L"kernel32.dll",reason=THREAD_DETACH,res=(nil)) | 0023:Ret PE DLL (proc=0x404c8980,module=0x40480000 L"kernel32.dll",reason=THREAD_DETACH,res=(nil)) retval=1 | 0023: *killed* exit_code=0 -(Main). Finishes its message processing and the waits: | 0009:Call kernel32.WaitForSingleObject(000000cc,ffffffff) ret=004ed693 | 0009: select( flags=4, cookie=0x406cf4e0, timeout=0, handles={0xcc} ) | 0009: select() = PENDING And this wait never returns until explicitly killed: | 0009: *killed* exit_code=0 I looked at many of these sequences. In all of them the subthread finished well before the main thread executed its Wait. I was looking for timing differences between the processing of the two threads, checking whether and when the WM_NULL message gets processed. Nothing seems to stand out. Any suggestions how to debug this? A large cut from the +relay,+server trace is on http://www.xs4all.nl/~rklazes/temp/agserver.log.bz2 Rein. -- Rein Klazes rklazes(a)xs4all.nl

2 4

Re: WineHQ: Update the Janitorial page
by Tom Nov. 18, 2003

Nov. 18, 2003

Dimitrie O Paun wrote > - <li> loader > - <li> loader/ne > - <li> memory > + <li class=committed> loader/ne > + <li class=committed> memory umm i'm lost here... - loader, but no committed on loader.. Tom

2 1

Can I turn off freetype at runtime
by Bill Medland Nov. 17, 2003

Nov. 17, 2003

Is it possible to turn off the freetype use at runtime, e.g. by changing something in the config file? Basically under SuSE several dialogs are drawing with 5 pixel text whereas under Windows they are about 9 pixel high (which I don't understand because I think that they should not exceed 8). Under RedHat they are 7 pixel which are at least readable. I hope that if I can turn off the freetype then on SuSE it will get the same font as on RedHat I tried setting an Alias but it didn't make any difference; it still used the same font instead of the alias -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed

3 2

Re: listbox: ownerdraw fix
by Dimitrie O. Paun Nov. 17, 2003

Nov. 17, 2003

On November 17, 2003 07:33 am, Huw D M Davies wrote: > - LISTBOX_RepaintItem( hwnd, descr, i, ODA_SELECT ); > + if (!IS_OWNERDRAW(descr)) > + LISTBOX_RepaintItem( hwnd, descr, i, ODA_SELECT ); > + else > + LISTBOX_InvalidateItemRect(hwnd, descr, i); > + Why not simply invalidate rect always, even when not in owner draw? -- Dimi.

2 4

[Fwd: LinuxQuestions.org Members Choice nomination]
by Mike Hearn Nov. 17, 2003

Nov. 17, 2003

Hey, an award never hurts. -------- Original Message -------- Subject: LinuxQuestions.org Members Choice nomination Date: Sun, 16 Nov 2003 18:03:58 -0500 (EST) From: Jeremy <jeremy(a)linuxquestions.org> To: mike(a)theoretic.com CC: michael.hearn(a)durham.ac.uk Mike, Just wanted to let you know that wine was nominated for Windows on Linux App of the Year in the 2003 LinuxQuestions.org Members Choice Awards. http://www.linuxquestions.org/questions/showthread.php?s=&threadid=116387 --jeremy

1 0

wine-pthread hangs
by Jeremy Shaw Nov. 17, 2003

Nov. 17, 2003

Hello, I was trying to run wine-pthread, but it hangs immediately after startup -- I can't even hit cntl-c to exit. If I try to run it under gdb, it seg faults. A backtrace looks like: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 14857)] 0x40040fd9 in __errno_location () from /lib/libpthread.so.0 (gdb) bt #0 0x40040fd9 in __errno_location () from /lib/libpthread.so.0 #1 0x40515ae6 in DOSFS_ToDosFCBFormat () from /usr/lib/wine/kernel32.dll.so #2 0x40516223 in DOSFS_FindUnixName () from /usr/lib/wine/kernel32.dll.so #3 0x40516f21 in DOSFS_GetFullName () from /usr/lib/wine/kernel32.dll.so #4 0x4051e8c9 in CreateFileW () from /usr/lib/wine/kernel32.dll.so #5 0x4021c879 in RtlDoesFileExists_U () from /usr/lib/wine/ntdll.dll.so #6 0x4021cedf in RtlDosSearchPath_U () from /usr/lib/wine/ntdll.dll.so #7 0x40218862 in LdrGetProcedureAddress () from /usr/lib/wine/ntdll.dll.so #8 0x40218c1c in LdrGetProcedureAddress () from /usr/lib/wine/ntdll.dll.so #9 0x40216c80 in _aullrem () from /usr/lib/wine/ntdll.dll.so #10 0x402170d3 in _aullrem () from /usr/lib/wine/ntdll.dll.so #11 0x4021984b in LdrInitializeThunk () from /usr/lib/wine/ntdll.dll.so #12 0x405511e4 in SetThreadExecutionState () from /usr/lib/wine/kernel32.dll.so (gdb) I am using the latest wine from CVS (as of 5pm, 11/14/2003). Linux 2.4.22 libc6 2.3.2 Do I need to do something special to get this working? I am trying to use wine-pthread because I want to use the winejack driver. The winejack driver does not work correctly with wine-kthread, because in libjack, there is a call to pthread_create which never returns. According to usenet, this could happen because wine-kthread is not linked against libpthread explicitly. I tried adding an explicit -lpthread to wine-kthread, but this just cause wine-kthread to hang (similar to wine-pthread, but in a different location). I also tried running ./configure --enable-nptl and installing a version of libc with nptl support, but I think nptl requires features added in 2.5.x -- so this was probably just wishful thinking. Thanks! Jeremy Shaw.

4 9

Re: Localization to portguese - winecfg (with patch)
by Mike Hearn Nov. 16, 2003

Nov. 16, 2003

Well, I don't have any real problem with it, but as I said before it's pretty pointless IMHO. The GUI is going to start changing again when I next get time to work on it (unfortunately not anytime soon in the foreseeable future), so you'll have to update it all over again. What winecfg needs now is code rather than strings.... On Sat, 15 Nov 2003 15:43:18 -0300, Sir Marcelo Duarte scribed thus: > I updated the resources of winecfg. If Mike Hearn don't disagree with this. > > Changelog: > Marcelo Duarte <wine-devel(a)bol.com.br> > - Localization to portguese - winecfg.

2 1

Re: wrc doesn't seem to accept -r option,even though it is automatically generated by make file
by Parzival Herzog Nov. 15, 2003

Nov. 15, 2003

On November 10, 2003 15:34, Ivan Leo Murray-Smith wrote: > You can easily upgrade to the october build, a GUI (winesetuptk) can write > the config for you, see > www003.portalis.it/115/ I am sending you email, because your message did not appear on the mailing list, so I can't respond to it there. I hope this is OK with you. As I said in the original post, I am not a wine "developer" (too ignorant for that), I am a (potential) user of the wine library, and the wine-user list people seemed to think my question was for wine-devel. At this point I don't even know if I have a bug or some finger-trouble, and if I have a bug, it is with an old version, yet a newer version gives me big problems, so I dont't want to go to the bug report stage if all I am doing is making some stupid mistake. The link http://prdownloads.sourceforge.net/wine/wine-20031016-mdk9.1.i586.rpm?downl… is broken. The latest rpm there for Mandrake is dated 20030911. I believe that is the version I downloaded and which would crash on starting my programs, which as I said, is the reason I reverted back to the version that came with Mandrake 9.1. There is no Mandrake rpm at Sourceforge for wine-devel, so which wine-devel rpm should I use? Given that I can obtain a complete set of compatible rpms, do I need to un-install my present wine installation? What will happen to my .wine directory? Will the old config info be used, or will it confuse the new installation? I have my own "wine" directory, under which is my own assembly of a "windows" installation, which took some time to get right. Should I keep this? -- Parzival Herzog

2 1

looking for some help with DIB code from WINE
by Jonathan Wilson Nov. 15, 2003

Nov. 15, 2003

I am working on ReactOS and would like to take the code in static void X11DRV_DIB_SetImageBits_RLE4( int lines, const BYTE *bits, DWORD width, DWORD dstwidth, int left, int *colors, XImage *bmpImage ) and static void X11DRV_DIB_SetImageBits_RLE8( int lines, const BYTE *bits, DWORD width, DWORD dstwidth, int left, int *colors, XImage *bmpImage ) And use it as a jumping-off point to add support for RLE butmaps into ReactOS. Looking at the parameters, I can see that: XImage *bmpImage is the image itself (basicly, I guess its the X11 equivelent of a HDC or a HBITMAP or something) int *colors is the color table and const BYTE *bits is the bits themselves. since ReactOS is only going to uncompress and store the bitmap bits, we dont need to worry about the color table or the XImage Anyhow, what I want to know is what the int lines, DWORD width, DWORD dstwidth, and int left parameters to these 2 functions mean.

1 0

Re: Wintab32 - Tablet support
by Robert Shearman Nov. 15, 2003

Nov. 15, 2003

> Hi, > > This is more a question for the developers.... Should have posted to wine-devel then :) Doing so now. > A couple of months ago there was a patch from Aric Stewart that added > support for graphics tablets in wine. However I have not heard anything > about it since. Is anybody still working on this? > Graphics tablet > support is the only thing stopping us from using Photoshop under Linux > at the present time. Moving all our graphics artists off dual booting > windows machines would be extremely benificial! > > I tried the original patch but found it affected the > stability of wine... I noticed that in the original patch a lot of functions were called from DllMain that shouldn't be called from there. Did the backtrace include wintab32.DllMain? The initialisation should probably be moved to either each function with a line like "if (!initialised) Initialise();" Alexandre, how come this patch hasn't been included in Wine yet? Was it the problem stated here or something else? > Daire Rob

2 1