- Wine-Devel - list.winehq.org

Re: Re: Stuck on threading
by Pouech Eric DMI AEI CAEN April 8, 2003

April 8, 2003

> tid as a parameter for instance, and I can't see any way to switch the > current thread, despite the docs mentioning such a concept. which docs... this isn't implemented in winedbg another solution for this would be using gdb thru winedbg (run winedbg -- --gdb) you'll get gdb as a front end, but communicating thru winedbg to the wineserver using gdb commands, you might be able to control a bit more the threads A+

2 1

Re: IP Multicast
by Mike Hearn April 8, 2003

April 8, 2003

Anything wrong with this one? FYI it uses a different structure to the original (rejected) patch from Marcus. thanks -mike On Tue, 2003-04-01 at 13:54, Mike Hearn wrote: > Hi, > > This patch adds support for IP multicast sockets to winsock. I stole > liberally from a patch from the summer of 2001 from Marcus, so thanks to > him for that: > > http://www.winehq.com/hypermail/wine-patches/2001/07/0009.html > > ChangeLog: > - Map winsock sockopts to the POSIX equivalents for IP multicast > - Remap winsock1 constant values to winsock2 using a forwarder function > - Change a FIXME to a TRACE, it appeared to be simply reporting progress > > thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 2

Stuck on threading
by Mike Hearn April 8, 2003

April 8, 2003

Hi, I'm a bit stuck. I have a DLL that does a FindWindow on DLL attach, and as part of that it does a GetWindowText which tries to send a message to another thread, using send_inter_thread_message. Other threads then attempt to load a DLL and the loader section prompty deadlocks. In gdb, if I attach at this point I can see a nice backtrace of the thread waiting for the reply to its WM_GETTEXT message, along with the thread ID. I'd quite like to see what the thread it sent the message to is doing, but for some reason in gdb "info threads" doesn't do anything and "thread 18" says, thread ID not known, despite it clearly being there in the backtrace: #5 0x40abd0cf in send_inter_thread_message (dest_tid=18, info=0x4072187c, res_ptr=0x40721874) at message.c:1719 So, I'm wondering if this is due to the funny games Wine plays with threads, I'm on a standard glibc 2.2 system by the way. For some reason I can't use winedbg because it stops with a load of exceptions inside the DLL that seem to be red herrings. Is there any way of switching to a wine thread using gdb to get a backtrace? Is there a sneakier approach I can use to find out why thread 18 has apparently deadlocked? There is probably a race condition here - this program will start some times but not others :( Has anybody got any tips on how to debug this sort of thing? thanks -mike -- Mike Hearn <m.hearn(a)signal.qinetiq.com> QinetiQ - Malvern Technology Center

3 2

Building WINE with other headers
by Steven Edwards April 8, 2003

April 8, 2003

Hello, I know we have discussed this before and Dimi put it on the Janitorial site but I dont think we ever came a conclusion on it and I could not find a easy fix. Last time I tried to change the include path manualy I ran in to lots of problems. I would like to attempt to build parts of WINE with only the mingw headers and exclude the winehq headers so I can: 1. Find out where the mingw w32api package is broken. 2. Impove the Wine headers if they are wrong. 3. Not use the winehq headers for the ReactOS (We wont try this untill 1 and 2 are in sync) BTW thanks for the winsock.h patch, it is nice to not have to have a simple command line now. Sorry for the head-ache <g> Steven

2 1

Visual FoxPro 8 / Wine20030318 crash
by Paul McNett April 8, 2003

April 8, 2003

I crash when building an EXE in the new version of Visual Foxpro. Any ideas? "windows" = "nt351", all dlls built-in. Here's the output leading up to the crash: fixme:hook:NotifyWinEvent (32769,0x50032,1,0)-stub! fixme:pidl:SHLogILFromFSIL (pidl=0x4032b090) fixme:dc:LockWindowUpdate (0x50033), partial stub! fixme:shell:ISVBgCm_fnGetCommandString unknown command string fixme:shell:ISVBgCm_fnGetCommandString unknown command string fixme:shell:ISVBgCm_fnGetCommandString unknown command string fixme:dc:LockWindowUpdate ((nil)), partial stub! fixme:shell:ReadCabinetState 0x4071e2e0 0x000c stub fixme:hook:NotifyWinEvent (32773,0x30031,7,1)-stub! fixme:hook:NotifyWinEvent (32768,0x90032,1,0)-stub! fixme:hook:NotifyWinEvent (32769,0x90032,256,0)-stub! fixme:hook:NotifyWinEvent (32769,0x90032,1,0)-stub! fixme:ole:DispCallFunc Do not know how to handle pvargResult 0x4071e5cc. Expect crash ... fixme:ole:DispCallFunc Method returned 0 err:ole:TLB_ReadTypeLib Loading of typelib L"E:\\src\\vfp\\sbs\\sbs.exe" failed with error 0 fixme:seh:EXC_RtlRaiseException call to unimplemented function kernel32.dll.BeginUpdateResourceA fixme:process:CreateProcessA (E:\prg\vfp8\dw15.exe,...): NORMAL_PRIORITY_CLASS ignored fixme:process:CreateProcessA (E:\prg\vfp8\dw15.exe,...): CREATE_DEFAULT_ERROR_MODE ignored fixme:win32:PE_CreateModule Security directory ignored fixme:ntdll:NtQuerySystemInformation (0x00000005,0x4028d858,0x00010000,(nil)) stub fixme:win32:PE_CreateModule Security directory ignored fixme:advapi:RegisterEventSourceW ((null),L"Microsoft Visual FoxPro"): stub fixme:advapi:ReportEventA stub fixme:advapi:DeregisterEventSource (0x1): stub fixme:wininet:InternetGetConnectedState always returning LAN connection. -- Paul McNett Liberal Earthling

4 5

NTPL & pthreads locks
by Dimitrie O. Paun April 8, 2003

April 8, 2003

Alexandre, If I understand correctly, we currently implement the pthreads locks on top on Wine locks because the standard pthreads locks are not powerful enough to support all Win32 locking primitives. Integrating these locks is necessary for integrating Wine with the pthreads Universe. Now, given the new NTPL work, would it be possible/feasible/desirable to implement the Win32 locks on top of NTPL primitives (such as futexes)? At the very least it makes the setup a lot more intuitive, and less likely to break. If we are to follow this path, there are portability problems. But do we support this sort of libc integration of Solaris and *BSD? And it seems to me that it shouldn't be too hard for these systems to provide something that would allow us to implement all Win32 locking primitives, and the end result would be a lot less brittle. -- Dimi.

3 3

Re: Re: cleaning the source tree when compiling outside the source tree
by Pouech Eric DMI AEI CAEN April 8, 2003

April 8, 2003

> I don't think we should do that. IMO we must not modify the source > tree in any way when building in a separate dir. It depends which files we're talking about I think that *~ (and any editor backup files), *rej* *orig* (patch leftovers), .#* (cvs update leftovers) should be removed from the source tree perhaps we need to seperate the semantics from clean and distclean. but at least, from a distclean point of view, I do think it would be great to remove the hereabove mentionned files from the source tree A+

2 1

re: hi wine team
by Dan Kegel April 8, 2003

April 8, 2003

> did the wine team consider construct the win32 support (wine) within a > micro-kernel architecture, just like the microsoft`s interix ? "Just like microsoft's Interix"? We have no idea how Microsoft implemented that stuff; it's not bundled with Windows, so not many people see it, and it's closed source, so it's a bit hard to distinguish a microkernel from a regular kernel. Please post some code so we know you're not a troll :-) - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

1 0

--with-nptl and RH 8 : unhappy
by Sylvain Petreolle April 8, 2003

April 8, 2003

Having RH 8.0 with glibc-2.3.2, I tried to compile Wine wiht --with-nptl. Wine compiles fine but doesnt run at all. Every application I try to run calls the debugger in a loop. [syl(a)snoop c]$ wine --debugmsg +relay notepad trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... trace:relay:RELAY_InitDebugLists RelayInclude = L"user32.CreateWindowA" trace:relay:RELAY_InitDebugLists RelayExclude = L"RtlEnterCriticalSection;RtlLeaveCriticalSection;_LeaveSysLevel;_EnterSysLevel" wine: Unhandled exception, starting debugger... err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 [syl(a)snoop c]$ err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec16 err:seh:EXC_DefaultHandling Unhandled exception code c000013a flags 0 addr 0x402fec98 ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

3 3

winelib/mfc queries
by KK singh April 8, 2003

April 8, 2003

I am using 20030318 build of wine ... 1. WINE_UNICODE_TEXT is no longer defined anywhere in any of the header files ? What should i do now with OLESTR ? 2. Should i define _AFXDLL while compiling mfc ? Regards kks __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com

2 1