December 2005 - Wine-Devel - list.winehq.org

Re: trouble with uxtheme dll

by Stefan Leichter

Am Samstag, 3. Dezember 2005 18:59 schrieb Marcus Meissner: > On Sat, Dec 03, 2005 at 06:16:48PM +0100, Stefan Leichter wrote: > > Hi, > > > > i am a little confuse about the uxtheme dll. I have a program that raises > > an execption after each call (not the return!) to the ordinal 1 of the > > dll. The strange thing is the relay log shows up to eight arguments for > > the function call, but according to the spec file of the uxtheme dll the > > function does not have any argument. Also the implemantation is only a > > stub which should not crash. > > > > Here an example for the call: > > > > 000b:Call uxtheme.1(00000090,42865450,0001aa9b,406acef4,00000000) > > ret=41ebcca5 trace:seh:__regs_RtlRaiseException code=c0000005 flags=0 > > addr=(nil) > > > > Does anyone have a wild guess what happend here? > > Its actually calling number 2 from the .spec file perhaps, OpenThemeFile. > > And the :seh: might be from the relay string printing code? I don't know. > As i understand you, the ordinals of uxtheme dll displayed in the relay trace are wrong. Different function calls (according to the number of arguments) in the relay log are displayed as function with the ordianl 1. Some more examples: 000b:Call uxtheme.1(4069ebf4) ret=41e4d04b trace:seh:__regs_RtlRaiseException code=c0000005 flags=0 addr=(nil) 000b:Call uxtheme.1(4069e7cc,00000000,00000000) ret=41e4c2da trace:seh:__regs_RtlRaiseException code=c0000005 flags=0 addr=(nil) 000b:Call uxtheme.1 (41f8d0f8,80000000,00000003,00000000,00000003,00000080,00000000) ret=41e4c7c0 trace:seh:__regs_RtlRaiseException code=c0000005 flags=0 addr=(nil) 000b:Call uxtheme.1(0000006c,42a76370,00000000,406acddc,427f4880,406acdcc) ret=41e4e21c trace:seh:__regs_RtlRaiseException code=c0000005 flags=0 addr=(nil) But why is this only a problem of uxtheme dll. The ordinals of comctl32 and kernel32 are displayed properly. Bye Stefan

Dec. 4, 2005

Re: Debugging winelib apps in Eclipse

by Boaz Harrosh

Michael Ost wrote: > Does anyone know how to set up Eclipse to debug winelib applications? > > I tried just replacing 'gdb' with 'winedbg' on the "Debugger" tab on the > "Debug" window. After Eclipse says "Launching..." there is an error that > says "Process terminated." > > After reviewing the winelib debug docs, I found that there is a --gdb > switch to winedbg so I added that as a "C/C++ Program Argument" on the > "Arguments" tab of the same window... a long shot, and it didn't work. > > This is on Fedora Core 4, with Eclipse 3.1 (yum updated from the 3.1M6 > version that comes with FC4), and with the wine 0.99.2 FC4 rpm. > > Any leads? Thanks ... mo > There is no need to use winedbg for a winelib application. The only advantage for that is the heap-walk, thread-walk and other special winedbg commands that will be hard to reach from the GUI. The disadvantage is that it is not compatible enough and breaks the GUI. Just use gdb it can understand all your symbols and wine's. What you need to do is run wine-kthread or wine-pthread directly. Check in your ps when you run a wine application what actually loads. Free Life Boaz

Dec. 4, 2005

Re: Make check failure

by James Hawkins

On 12/3/05, Dustin Navea <speeddymon(a)gmail.com> wrote: > make[3]: Entering directory `/home/speeddy/wine/dlls/advapi32/tests' > ../../../tools/runtest -q -P wine -M advapi32.dll -T ../../.. -p > advapi32_test.exe.so crypt.c && touch crypt.ok > crypt.c:710: Test failed: expected 234, got 0 > > > Anyone wanna help me figure out why? > I'm not at my computer so I can test it, but I'd put money on this patch being the cause of failure: Remove some Unicode->ANSI cross-calls in crypt functions. I'll work on it when I get home. -- James Hawkins

Dec. 4, 2005

Re: Why Steam fails [VirtualAlloc]

by Rob Shearman

Ivan Gyurdiev wrote: >> I tries that with the exact same results... >> Attempted mmap_anon of size 200MB...fails...Steam fails, with ENOMEM. >> > Here's the exact mmap call... it's the only one that fails, and it's > the largest without MAP_NORESERVE. > > mmap2(NULL, 209780736, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = > -1 ENOMEM (Cannot allocate memory) You've probably got a fragmented address space caused by having a lot of dynamic libraries loaded at different addresses... > Running the same call from a test program suceeds - I can mmap() > things that are an order of magnitude larger without problems (as a > regular user). ...which doesn't happen in your test program as it doesn't use as many. Remember that it takes only one page of memory sitting at the wrong virtual memory address to divide the available contiguous addresses in half. I would suggest playing around with the prelink tool to put dynamic libraries in better positions in memory. Rob

Dec. 4, 2005

Re: iTunes COM problems?

by Rob Shearman

Thomas Meyer wrote: >Hi. > >iTunes version 6 installation fails. i made a log an my guess is that the problem is here: > >[snip] >trace:ole:TMStubImpl_AddRef (0x7fdcd028)->(ref before=1) >trace:ole:stub_manager_int_release after 1 >trace:ole:dispatch_rpc Calling apartment thread 0x0000000b... >trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0400 >trace:ole:TMStubImpl_Invoke ... >trace:ole:ITypeLib2_fnAddRef (0x7fd8a348)->ref was 9 >trace:ole:ITypeInfo_fnAddRef (0x7fdc8b30)->ref is 3 >trace:ole:ITypeInfo_fnGetFuncDesc (0x7fdc8b30) index 0 >trace:ole:ITypeInfo_fnGetFuncDesc (0x7fdc8b30) index 1 >trace:ole:ITypeInfo_fnGetDocumentation (0x7fdc8b30) memid -1 Name(0x7fbda55c) DocString((nil)) HelpContext((nil)) HelpFile((nil)) >trace:ole:ITypeInfo_fnGetNames (0x7fdc8b30) memid=0x60010001 Maxname=10 >trace:ole:deserialize_param vt 3 at 0x7fdd193c >trace:ole:_invoke Calling 0x4136dc(7ced8370,0000005f,) >trace:ole:_invoke returns 00000000 >trace:ole:serialize_param (tdesc.vt 3) >trace:ole:ITypeInfo_fnRelease (0x7fdc8b30)->(2) >trace:ole:ITypeLib2_fnRelease (0x7fd8a348)->(9) >trace:ole:TMStubImpl_Invoke returning >trace:ole:TMStubImpl_Release (0x7fdcd028)->(ref before=2) >trace:ole:apartment_release a0000000b: after = 1 >trace:ole:rpc_sendreceive_thread completed with status 0x0 >trace:ole:DllMain 0x7f6e0000 0x3 (nil) ole32.dll >trace:ole:CoWaitForMultipleHandles -- 0x00000000 >trace:ole:RpcChannelBuffer_SendReceive RPC call status: 0x0 >trace:ole:RpcChannelBuffer_SendReceive -- 0x00000000 >trace:ole:ITypeInfo_fnRelease (0x7fe2e6f0)->(2) >trace:ole:ITypeLib2_fnRelease (0x7fdf4758)->(201) > >Ok. One of the things i did't figured out till now. What does this xCall thing mean? > >trace:ole:xCall -- 0x00000000 >trace:ole:CoMarshalInterface (0x775af1b8, {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, 0x7ce45480, 3, (nil), MSHLFLAGS_TABLESTRONG) >trace:ole:CoGetStandardMarshal ({c9ce9778-210c-4cb4-b4f0-f589c3dda00b},0x7ce45480,3,(nil),1,0x7fbde72c) >trace:ole:CoMarshalInterface Using standard marshaling >trace:ole:CoMarshalInterface Calling IMarshal::MarshalInterace >trace:ole:StdMarshalImpl_MarshalInterface (...,{c9ce9778-210c-4cb4-b4f0-f589c3dda00b},...) >trace:ole:CoGetPSClsid () riid={c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, pclsid=0x7fbde654 >trace:ole:WINE_StringFromCLSID 0x496980->{C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} >trace:ole:__CLSIDFromStringA {C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} -> 0x7fbde654 >trace:ole:CoGetPSClsid () Returning CLSID={c9ce9778-210c-4cb4-b4f0-f589c3dda00b} > >trace:ole:get_facbuf_for_iid CoGetPSClsid hr= 0x00000000 >trace:ole:CoGetClassObject > CLSID: {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, > IID: {d5f569d0-593b-101a-b569-08002b2dbf7a} >trace:ole:WINE_StringFromCLSID 0x7fbde654->{C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} >trace:ole:COMPOBJ_DLLList_Add >trace:ole:get_inproc_class_object DllGetClassObject hr= 0x80040111 > >err:ole:CoGetClassObject no class object {c9ce9778-210c-4cb4-b4f0-f589c3dda00b} could be created for for context 0x1 >err:ole:marshal_object couldn't get IPSFactory buffer for interface {c9ce9778-210c-4cb4-b4f0-f589c3dda00b} > >I guess this is the reason why the installer fails. Maybe i am wrong and this is an error in the application program. but how to determin this? > > Yes, this is likely the reason. Let me guess, you are trying with a version of Wine that is more than a week old? Have you tried with the current CVS? >is there a way to explorer all interfaces in an COM object (in the dll file)? > > Not really. One way may be to disassemble the DllGetClassObject function, but that would be more trouble than it's worth. >err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80040111 >err:ole:CoMarshalInterface Failed to marshal the interface {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, 80040111 >trace:ole:CoMarshalInterface completed with hr 0x80040111 > > <snip> >by the way: what is an apartment? (i think it has something to do with thread/process, therefore i added the dll names for each Main call) > > It is a unit in which COM objects are valid and is equal to or larger than a thread, but smaller than or equal to a process. In practical terms, it means that when you uninitialize an apartment all of the COM objects that it exports are released and can no longer be accessed, and similarly proxies to remote objects are invalidated and just return RPC_E_DISCONNECTED. Hope this helps, Rob

Dec. 4, 2005

[Take 2] Make check error

by Dustin Navea

The last error was caused by linux/capi.h being included, even though it wont compile (checked configure) This one I'm not sure about. ../../../tools/runtest -q -P wine -M gdi32.dll -T ../../.. -p gdi32_test.exe.so metafile.c && touch metafile.ok metafile.c:135: Test failed: pass 0: dx[0] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[1] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[2] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[3] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[4] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[5] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[6] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[7] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[8] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[9] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[10] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[11] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[12] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[13] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[14] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[15] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[16] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[17] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[18] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[19] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[20] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[21] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[22] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[23] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[24] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[25] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[26] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[27] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[28] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[29] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[30] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[31] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[32] (0) didn't match 5 metafile.c:135: Test failed: pass 0: dx[33] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[34] (0) didn't match 6 metafile.c:135: Test failed: pass 0: dx[35] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[36] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[37] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[38] (0) didn't match 3 metafile.c:135: Test failed: pass 0: dx[39] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[40] (0) didn't match 2 metafile.c:135: Test failed: pass 0: dx[41] (0) didn't match 4 metafile.c:135: Test failed: pass 0: dx[42] (0) didn't match 4 fixme:dc:GdiIsMetaPrintDC (nil) fixme:dc:GdiIsPlayMetafileDC (nil) fixme:dc:GdiIsMetaPrintDC 0x358 fixme:dc:GdiIsPlayMetafileDC 0x358 fixme:dc:GdiIsMetaPrintDC 0x368 fixme:dc:GdiIsPlayMetafileDC 0x368 make[3]: *** [metafile.ok] Error 43 make[3]: Leaving directory `/home/speeddy/wine/dlls/gdi/tests' make[2]: *** [tests/__test__] Error 2 make[2]: Leaving directory `/home/speeddy/wine/dlls/gdi' make[1]: *** [gdi/__test__] Error 2 make[1]: Leaving directory `/home/speeddy/wine/dlls' make: *** [dlls/__test__] Error 2

Dec. 4, 2005

Re: Why Steam fails [VirtualAlloc]

by Mike Hearn

On Sat, 03 Dec 2005 15:38:10 -0500, Ivan Gyurdiev wrote: > Running the same call from a test program suceeds - I can mmap() things > that are an order of magnitude larger without problems (as a regular user). How big is your swapfile? It should probably have a MAP_NORESERVE flag.

Dec. 4, 2005

Make check failure

by Dustin Navea

make[3]: Entering directory `/home/speeddy/wine/dlls/advapi32/tests' ../../../tools/runtest -q -P wine -M advapi32.dll -T ../../.. -p advapi32_test.exe.so crypt.c && touch crypt.ok crypt.c:710: Test failed: expected 234, got 0 Anyone wanna help me figure out why? Dustin

Dec. 4, 2005

iTunes COM problems?

by Thomas Meyer

Hi. iTunes version 6 installation fails. i made a log an my guess is that the problem is here: [snip] trace:ole:TMStubImpl_AddRef (0x7fdcd028)->(ref before=1) trace:ole:stub_manager_int_release after 1 trace:ole:dispatch_rpc Calling apartment thread 0x0000000b... trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0400 trace:ole:TMStubImpl_Invoke ... trace:ole:ITypeLib2_fnAddRef (0x7fd8a348)->ref was 9 trace:ole:ITypeInfo_fnAddRef (0x7fdc8b30)->ref is 3 trace:ole:ITypeInfo_fnGetFuncDesc (0x7fdc8b30) index 0 trace:ole:ITypeInfo_fnGetFuncDesc (0x7fdc8b30) index 1 trace:ole:ITypeInfo_fnGetDocumentation (0x7fdc8b30) memid -1 Name(0x7fbda55c) DocString((nil)) HelpContext((nil)) HelpFile((nil)) trace:ole:ITypeInfo_fnGetNames (0x7fdc8b30) memid=0x60010001 Maxname=10 trace:ole:deserialize_param vt 3 at 0x7fdd193c trace:ole:_invoke Calling 0x4136dc(7ced8370,0000005f,) trace:ole:_invoke returns 00000000 trace:ole:serialize_param (tdesc.vt 3) trace:ole:ITypeInfo_fnRelease (0x7fdc8b30)->(2) trace:ole:ITypeLib2_fnRelease (0x7fd8a348)->(9) trace:ole:TMStubImpl_Invoke returning trace:ole:TMStubImpl_Release (0x7fdcd028)->(ref before=2) trace:ole:apartment_release a0000000b: after = 1 trace:ole:rpc_sendreceive_thread completed with status 0x0 trace:ole:DllMain 0x7f6e0000 0x3 (nil) ole32.dll trace:ole:CoWaitForMultipleHandles -- 0x00000000 trace:ole:RpcChannelBuffer_SendReceive RPC call status: 0x0 trace:ole:RpcChannelBuffer_SendReceive -- 0x00000000 trace:ole:ITypeInfo_fnRelease (0x7fe2e6f0)->(2) trace:ole:ITypeLib2_fnRelease (0x7fdf4758)->(201) Ok. One of the things i did't figured out till now. What does this xCall thing mean? trace:ole:xCall -- 0x00000000 trace:ole:CoMarshalInterface (0x775af1b8, {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, 0x7ce45480, 3, (nil), MSHLFLAGS_TABLESTRONG) trace:ole:CoGetStandardMarshal ({c9ce9778-210c-4cb4-b4f0-f589c3dda00b},0x7ce45480,3,(nil),1,0x7fbde72c) trace:ole:CoMarshalInterface Using standard marshaling trace:ole:CoMarshalInterface Calling IMarshal::MarshalInterace trace:ole:StdMarshalImpl_MarshalInterface (...,{c9ce9778-210c-4cb4-b4f0-f589c3dda00b},...) trace:ole:CoGetPSClsid () riid={c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, pclsid=0x7fbde654 trace:ole:WINE_StringFromCLSID 0x496980->{C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} trace:ole:__CLSIDFromStringA {C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} -> 0x7fbde654 trace:ole:CoGetPSClsid () Returning CLSID={c9ce9778-210c-4cb4-b4f0-f589c3dda00b} trace:ole:get_facbuf_for_iid CoGetPSClsid hr= 0x00000000 trace:ole:CoGetClassObject CLSID: {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, IID: {d5f569d0-593b-101a-b569-08002b2dbf7a} trace:ole:WINE_StringFromCLSID 0x7fbde654->{C9CE9778-210C-4CB4-B4F0-F589C3DDA00B} trace:ole:COMPOBJ_DLLList_Add trace:ole:get_inproc_class_object DllGetClassObject hr= 0x80040111 err:ole:CoGetClassObject no class object {c9ce9778-210c-4cb4-b4f0-f589c3dda00b} could be created for for context 0x1 err:ole:marshal_object couldn't get IPSFactory buffer for interface {c9ce9778-210c-4cb4-b4f0-f589c3dda00b} I guess this is the reason why the installer fails. Maybe i am wrong and this is an error in the application program. but how to determin this? is there a way to explorer all interfaces in an COM object (in the dll file)? err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80040111 err:ole:CoMarshalInterface Failed to marshal the interface {c9ce9778-210c-4cb4-b4f0-f589c3dda00b}, 80040111 trace:ole:CoMarshalInterface completed with hr 0x80040111 trace:ole:CreateFileMoniker (L"{872653C6-5DDC-488B-B7C2-CF9E4D9335E5}",0x7fbde880) trace:ole:FileMonikerImpl_Construct (0x775af1b8,L"{872653C6-5DDC-488B-B7C2-CF9E4D9335E5}") trace:ole:FileMonikerImpl_DecomposePath L"{872653C6-5DDC-488B-B7C2-CF9E4D9335E5}", (nil) trace:ole:FileMonikerImpl_QueryInterface (0x775af1b8,{0000000f-0000-0000-c000-000000000046},0x7fbde880) trace:ole:FileMonikerImpl_AddRef (0x775af1b8) trace:ole:CoCreateInstance (rclsid={064cb054-2518-474e-b2e8-200049528c42}, pUnkOuter=(nil), dwClsContext=00000004, riid={a16ab1e1-377d-4df2-8d8a-c9f283857ddc}, ppv=0x7fbde7cc) trace:ole:CoGetClassObject CLSID: {064cb054-2518-474e-b2e8-200049528c42}, IID: {00000001-0000-0000-c000-000000000046} trace:ole:RPC_GetLocalClassObject rclsid={064cb054-2518-474e-b2e8-200049528c42}, iid={00000001-0000-0000-c000-000000000046} trace:ole:WINE_StringFromCLSID 0x480b00->{064CB054-2518-474E-B2E8-200049528C42} trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" trace:ole:WINE_StringFromCLSID 0x480b00->{064CB054-2518-474E-B2E8-200049528C42} trace:ole:create_server activating local server L"c:\\PROG~1F2\\GEME~SR3\\INST~JM1\\Driver\\11\\INTE~MEX\\IDriverT.exe -Embedding" for {064cb054-2518-474e-b2e8-200049528c42} trace:ole:DllMain 0x7f910000 0x3 (nil) ole32.dll trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message __driCreateNewScreen_20050727 - succeeded trace:ole:DllMain 0x7f870000 0x1 0x1 ole32.dll trace:ole:DllMain (0x7f770000,1,0x1) oleaut32.dll trace:ole:DllMain 0x7f870000 0x2 (nil) ole32.dll trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:CoWaitForMultipleHandles received message whilst waiting for RPC: 0x0200 trace:ole:CoWaitForMultipleHandles waiting for rpc completion or window message trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:DllMain 0x7f910000 0x3 (nil) ole32.dll trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 trace:ole:RPC_GetLocalClassObject waiting for L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}" warn:ole:RPC_GetLocalClassObject Connecting to L"\\\\.\\pipe\\{064CB054-2518-474E-B2E8-200049528C42}", no response yet, retrying: le is 2 [installer contiunes here. but i did end the program; after a while the installer fails with an error message] by the way: what is an apartment? (i think it has something to do with thread/process, therefore i added the dll names for each Main call) any ideas and remarks are welcome thanks and regards Thomas ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

Dec. 3, 2005

Re: Why Steam fails

by James Liggett

On Sat, 2005-12-03 at 15:02 -0500, Ivan Gyurdiev wrote: > Stefan Dösinger wrote: > > Hello, > > > >> It doesn't seem to check the retval of the first alloc, which fails > >> about half of the time in > >> wine_anon_mmap (mmap() call) with ENOMEM. If the allocation succeeds, > >> Steam proceeds to run. > >> If it fails, Steam dies with the message above. > >> > > I just started Steam 5 times without a single failure. I can't reproduce the > > problem. > > > I think I'm the only one with that problem... and I can't figure out > what's wrong :( > >> Isn't this supposed to be a Virtual allocation...Why does it work one > >> time, and not the other... > >> The manpage for mmap() says ENOMEM can occur if the process exceeds its > >> allowed number of mappings. > >> Is this relevant? > >> > > Maybe you should check your /etc/limits file. Your distro might have limited > > the amount of memory a user may allocate. > > > > The limits are the default ones - all lines in that file are commented out. > > If you don't mind security risks, you could try to run Steam as root, and see > > if the problem continues. But back up your MBR first ; > > > I tries that with the exact same results... > Attempted mmap_anon of size 200MB...fails...Steam fails, with ENOMEM. Wow, thats really weird...I can also use steam without incident (I can even play Half-Life 2, the only issues I get are some intermittent sound lags.) Perhaps there's something wrong with your RAM? Have you tested any other apps that use about as much as Steam uses (about 200 MB max in my experience) on either WINE or native apps? James > > >

Dec. 3, 2005