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

error when running wine..
by JGraham March 18, 2003

March 18, 2003

has anyone gotten this message "err:module:get_registry_value Invalid load order module-type L"so", ignored"? it's been happening for me on current cvs builds. I have a clean fake windows and registry. so, i shouldn't be getting it.. thanks.

3 2

Re: Widl Fixes
by Ove Kaaven March 18, 2003

March 18, 2003

fre, 2003-03-07 kl. 19:49 skrev Jon: > This patch addresses some issues with widl. After applying the patch all .idl > files should be regenerated. These fixes are needed before my ocidl.idl can > be added. The last two lines of the changelog aren't seen in the wild; I > found them only when adding ocidl to my tree. Could you explain the reason behind the last line, "Don't dump full struct/enum definitions in prototypes", since this shouldn't happen in any case. When a prototype is emitted, the parameter type is supposed to be defined, or not; if it's not defined, t->defined is FALSE, and if it's defined, t->written should be TRUE, either of which should lead to the "else" clause which doesn't dump the full struct/enum definition. If t->written isn't TRUE, why isn't it? (And if there's a good reason for it after all, it would be cleaner to say "if (t->defined && !t->written && structs)" instead of adding a new "if (structs)" inside) > There is one remaining bug in widl which I haven't yet tracked down; someone > more knowledgable with widl may want to look at it: > > If objidl.idl is compiled with '-b' but without '-h', the resulting header > contains garbage ("[][][][][][][][][]" - generated by write_array() just > after IPropertyStorage_Stat_Stub) in the generated header. With both flags > (the default for Wine) however, the output is correct. I thought I had fixed such occurrences. If your widl is properly recompiled, then I'm not sure why it happens. > Also, it would be nice if widl handled function pointers as method args... I didn't think RPC supported this. The MS IDL I've seen just uses that cpp_quote #if 0 ... else trick to define structures with these, and I saw no need for widl to be smarter about it than MIDL is, considering that function pointers doesn't map cleanly to RPC anyway. Besides, it would be nice if our .idl files stayed compatible with MIDL.

2 4

Re: TreeView notifications fix
by John K. Hohm March 18, 2003

March 18, 2003

> Well, WinAmp seems to use CreateWindowExW to create the window, but I > can't find where the window class is registered, it doesn't seem to > appear in a +class trace anywhere. The string name is "#32770", so maybe > it's internal. Indeed, here is a list of system classes: Class Description ---------- -------------------------------------------------------------- ComboLBox The class for the list box contained in a combo box. DDEMLEvent Windows NT/Windows 2000/Windows XP: The class for Dynamic Data Exchange Management Library (DDEML) events. Message Windows 2000/Windows XP: The class for a message-only window. #32768 The class for a menu. #32769 The class for the desktop window. #32770 The class for a dialog box. #32771 The class for the task switch window. #32772 Windows NT/Windows 2000/Windows XP: The class for icon titles.

2 1

Wine crashes and floods shell with garbage
by Rok Mandeljc March 17, 2003

March 17, 2003

Anyone else has this problem? [mrok(a)mrok cdrom]# wine setup [mrok(a)mrok cdrom]# fixme:ntdll:MODULE_AllocModRef Trying to load second .EXE file: E:\AutoRun.exe fixme:ntdll:MODULE_AllocModRef Trying to load second .EXE file: E:\AutoRun.exe fixme:ntdll:MODULE_AllocModRef Trying to load second .EXE file: E:\AutoRun.exe @wine client error:0: T++\¤B `BÄ@ `BfBřýh(a)3ż@#äýh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfBŕëh(a)3ż @?@#Ěëh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfBČŮh(a)3ż @?@#´Ůh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfB°Çh(a)3ż @?@#Çh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfBµh(a)3ż @?@#µh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfBŁh(a)3ż @?@#lŁh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfBhh(a)3ż @?@#Th(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfBPh(a)3ż @?@#<h(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfB8mh(a)3ż @?@#$mh(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfB [h(a)3ż @?@#[h(a)+Ŕ3ż @wine client error:0: T++\¤B `BÄ@ `BfIh(a)3ż @? @#ôHh(a)+Ŕ3ż ... Looks like this happens when wine tries to run another process. Any ideas how to fix it?

2 1

Segfaults in RtlTryEnterCriticalSection ?
by Sylvain Petreolle March 17, 2003

March 17, 2003

What information could be usefull to debug a segfault in RtlTryEnterCriticalSection ? Since March beginning I have segfaults into programs that used to run before. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 8192 (LWP 8925)] 0x400ba904 in RtlTryEnterCriticalSection (crit=0x40240570) at ../../include/winbase.h:1918 1918 __asm__ __volatile__( ".byte 0x64\n\tmovl 0x24,%0" : "=r" (ret) ); (gdb) bt #0 0x400ba904 in RtlTryEnterCriticalSection (crit=0x40240570) at ../../include/winbase.h:1918 #1 0x4009355c in TryEnterCriticalSection (crit=0x40240570) at ../../memory/heap.c:814 #2 0x400b15f3 in __pthread_mutex_trylock (mutex=0x4212b180) at ../../scheduler/pthread.c:320 #3 0x42073999 in calloc () from /lib/i686/libc.so.6 #4 0x410c69e7 in s8790 () from /usr/X11R6/lib/modules/dri/fglrx_dri.so (gdb) list - 1908 { 1909 DWORD ret; 1910 __asm__ __volatile__( ".byte 0x64\n\tmovl 0x20,%0" : "=r" (ret) ); 1911 return ret; 1912 } 1913 1914 extern inline DWORD WINAPI GetCurrentThreadId(void); 1915 extern inline DWORD WINAPI GetCurrentThreadId(void) 1916 { 1917 DWORD ret; gdb) disass $pc-32 $pc+32 Dump of assembler code from 0x400ba8e4 to 0x400ba924: 0x400ba8e4 <RtlTryEnterCriticalSection+32>: or $0x74,%al 0x400ba8e6 <RtlTryEnterCriticalSection+34>: or %ecx,0x24348bc8(%ecx) 0x400ba8ec <RtlTryEnterCriticalSection+40>: leave 0x400ba8ed <RtlTryEnterCriticalSection+41>: ret $0x4 0x400ba8f0 <RtlTryEnterCriticalSection+44>: mov $0x1,%eax 0x400ba8f5 <RtlTryEnterCriticalSection+49>: lock xadd %eax,(%edx) 0x400ba8f9 <RtlTryEnterCriticalSection+53>: incl 0x8(%esi) 0x400ba8fc <RtlTryEnterCriticalSection+56>: mov $0x1,%ecx 0x400ba901 <RtlTryEnterCriticalSection+61>: jmp 0x400ba8e7 <RtlTryEnterCriticalSection+35> 0x400ba903 <RtlTryEnterCriticalSection+63>: nop 0x400ba904 <RtlTryEnterCriticalSection+64>: mov %fs:0x24,%eax 0x400ba90a <RtlTryEnterCriticalSection+70>: mov %eax,0xc(%esi) 0x400ba90d <RtlTryEnterCriticalSection+73>: movl $0x1,0x8(%esi) 0x400ba914 <RtlTryEnterCriticalSection+80>: jmp 0x400ba8fc <RtlTryEnterCriticalSection+56> 0x400ba916 <RtlTryEnterCriticalSection+82>: mov %esi,%esi 0x400ba918 <RtlLeaveCriticalSection>: push %ebp 0x400ba919 <RtlLeaveCriticalSection+1>: mov %esp,%ebp 0x400ba91b <RtlLeaveCriticalSection+3>: mov 0x8(%ebp),%ecx 0x400ba91e <RtlLeaveCriticalSection+6>: push %ebx 0x400ba91f <RtlLeaveCriticalSection+7>: mov 0x8(%ecx),%eax 0x400ba922 <RtlLeaveCriticalSection+10>: dec %eax 0x400ba923 <RtlLeaveCriticalSection+11>: call 0x400ba928 <RtlLeaveCriticalSection+16> End of assembler dump. ===== Sylvain Petreolle spetreolle(a)users.sourceforge.net Fight Spam ! EuroCauce: http://www.euro.cauce.org/en/index.html ICQ #170597259 "Don't think you are. Know you are." Morpheus, in "Matrix". ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 3

Re: winedos / Speed up RM software interrupt handling
by Alexandre Julliard March 17, 2003

March 17, 2003

Jukka Heinonen <jhei(a)iki.fi> writes: > This patch speeds up software interrupts in real mode > considerably, in addition to making interrupt handling simpler > (at least in my opinion). Instead of throwing an exception, > vm86 handler calls winedos callback as is done in case of > protected mode software interrupts. I think it would be cleaner to make __wine_enter_vm86 simply return in that case and let winedos deal with that. We don't want the signal handling to have to know about winedos if possible. -- Alexandre Julliard julliard(a)winehq.com

3 4

Re: Re Resend fix for ArrangeCtrlPositions in commdlg
by Tony Lambregts March 17, 2003

March 17, 2003

Maxime Bellengé wrote: > Here is the good one attached. Sorry for the trouble. > Please discard the previous one. > > a+ > > ChangeLog: > - Fix how the size of the dialog is computed and the child component > placed. > This one looks line wrapped as well (sorry) -- Tony Lambregts

3 2

Determining dll imports in dlls
by Brad Campbell March 17, 2003

March 17, 2003

G'day all, I'm using wine in a small control system to run a gui win32 program. I had an idea that I could determine what dll's this program used and only including the wine.dll.so files that were required to run this program. I started by doing a strings on the .exe file and using that to determine which .dlls it referenced. I thought I could use the same process to determine which dll's were then referenced by the dll's the .exe pulled in. Plus including the core dll's by default. Am I missing something, or will this work ? I'm in the process of developing a batch file to do it for me, is there a more accurate way of determining which dll's a dll references than doing a text search for dll names in the binary? -- Brad.... /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML MAIL / \

4 9

Re: DPRINTF->TRACE dlls/ddraw/dsurface/main.c
by Lionel Ulmer March 17, 2003

March 17, 2003

Just to nitpick, in most of your patches, you have this : > if (TRACE_ON(ddraw)) { > - DPRINTF(" Real caps are : "); DDRAW_dump_DDSCAPS2(&our_caps); DPRINTF("\n"); > + TRACE(" Real caps are : "); DDRAW_dump_DDSCAPS2(&our_caps); TRACE("\n"); > } As we use 'TRACE' now and not 'DPRINTF', the 'TRACE_ON' constructs could be removed. But well, one could say that it optimizes stuff to not do the test thrice :-) Lionel -- Lionel Ulmer - http://www.bbrox.org/

4 4

Re: Oleaut32 Debug Messages
by Dimitrie O. Paun March 17, 2003

March 17, 2003

On March 11, 2003 05:49 pm, Jon wrote: > - if (debugout) MESSAGE("%lx",*arg); > + if (debugout) TMSG2("%lx",*arg); This is just too ugly! Please don't do such code uglification to save a few bytes. Beyond that, why isn't this file using the standard TRACE macro? MESSAGEs should be very rare, and are intended for the user, as such there's no need to compile them out, ever. -- Dimi.

7 17