September 2002 - Wine-Devel

ANSI_CHARSET

by Jeff Smith

ANSI_CHARSET and SYMBOL_CHARSET need to be defined (in include/wingdi.h), but I have some doubts about the details. SYMBOL_CHARSET should be defined as (BYTE)2, I believe. If the current value of DEFAULT_CHARSET as (BYTE)1 is correct, then I suspect ANSI_CHARSET should be (BYTE)0. I question the current value of DEFAULT_CHARSET, and suspect it should be the reverse (DEFAULT:0 ANSI:1). DEFAULT defines tend to be 0 except for a few special cases (and this one does not fit as one of in my book). I'm sure someone out there is more familiar with this than I am, and I would appreciate their feedback. Notes: There is a function in shell32.dll as distributed in Win95-OSR-2.1, that uses the LOGFONT structure. In this function, the structure is used for three fonts: "Times New Roman", "Arial", and "Wingdings". The lfCharSet member for each case is 0, 0, and 2, respectively. -- Jeff Smith _________________________________________________________________ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com

Sept. 3, 2002

Re: current wine status pr-1

by Tony Lambregts

Paul Millar wrote: >Hi Tom, > > >On Mon, 2 Sep 2002, tom wrote: > > >>Paul Millar wrote: >> >> >>>On Sun, 1 Sep 2002, tom wrote: >>> >>> >>>>I have a pre-1 hacked together and request any feed back that you can give. >>>> >>>> >>>I'm doing rolling CVS regression/conformance testing and reporting back >>>whenever something breaks. How about adding an extra line under the "Wine >>>Regression Test Suite"? >>> >>> >>> >>Hi Paul, >> >>Is this ** Part ** of the Regression Test Suite or a different >>category to add ? >> >> > >It could probably be argued either way ... :) In the limited meaning of >Regression Test Suite, then the answer is no. > <picky> What we have called in the past as "the regression test suite" should be called "the conformance test suite". One of the things it is usefull for is to test for regressions but that is only one of its uses. Its primary purpose is to ensure that the behaviour of the wine API conforms to that of Windows API. </picky> It is great to see this page updated. Tony Lambregts

Sept. 3, 2002

Re: Problem with regression tests getting stuck

by Paul Millar

Hi Sylvian, On Fri, 30 Aug 2002, [iso-8859-1] Sylvain Petreolle wrote: > I recently tried to compile gcc 3.2 from sources on my RedHat 7.3. > It seems that it is a gcc 2.96 bug as tests now pass 100%. Actually, one of the annoying things about this is I've never managed to reproduce the bug in a "controlled" environment. Even repeatedly running the regression tests in a loop on the same machine and just waiting for it to freeze: nada! It only seems to happen during a WRT-update. There are some differences, but only in terms of pipes and filters: nothing that should affect the outcome. I could switch to gcc-3.1 and see if that fixes it but, as Mr Holmes would have it, absence of evidence is not evidence of absence :) Besides, too often I've seen some completely wacky behaviour of seemingly innocuous code (which I was convinced was because of compiler-error) only for some subtle code-related bug to turn out to be the culprit. That said, gcc-2.96 was/is a completely fscked up "release" of gcc. > (even if gcc 3.2 is a bit slower to compile wine;)) How much of a performance hit do you suffer here? > --- Paul Millar <paulm(a)astro.gla.ac.uk> a �crit�: > > Hi everyone, > > I've had the regression tests freeze on me again (see [1] for > > previous > > report). Sylvain has reported problems with the wininet regression > > tests > > (described in [2]). The symptoms are the same, but for me the problem > > is > > only intermittent. This time I caught the problem with gdb and > > obtained > > the following info: > > > > [...] > > Loaded symbols for /lib/libresolv.so.2 > > 0x402e7744 in __libc_close () at __libc_close:-1 > > -1 __libc_close: No such file or directory. > > in __libc_close > > (gdb) bt > > #0 0x402e7744 in __libc_close () at __libc_close:-1 > > #1 0x400ec9a4 in __DTOR_END__ () > > from /home/paulm/WINE-cvs/wine/dlls/libntdll.dll.so > > #2 0x400b3df5 in WaitForMultipleObjectsEx (count=0, handles=0x0, > > wait_all=0, > > timeout=100, alertable=0) at ../../scheduler/synchro.c:257 > > #3 0x400b3b88 in Sleep (timeout=100) at > > ../../scheduler/synchro.c:178 > > #4 0x40358747 in winapi_test (flags=268435456) at tests/http.c:121 > > #5 0x40358b36 in func_http () at tests/http.c:184 > > #6 0x40358f9d in run_test (name=0xbffffc63 "http.c") at wtmain.c:244 > > #7 0x40357037 in __wine_exe_main () at wininet_test.exe.spec.c:133 > > #8 0x400aff84 in start_process () at ../../scheduler/process.c:528 > > #9 0x400b3f3f in call_on_thread_stack (func=0x400afd2c) > > at ../../scheduler/sysdeps.c:108 > > > > So, to summarise (with some extra bits of information): > > > > The problem occurs when wininet/tests/http.c is testing asynchronous > > HttpSendRequest(), so flags > 0. The problem is triggered at line 121 > > of > > http.c, i.e.: > > 120 while ((flags)&&(!goon)) > > 121 Sleep(100); > > > > > > Sleep(), in turn, just calls WaitForMultipleObjectsEx(). From > > scheduler/synchro.c: > > 176 VOID WINAPI Sleep( DWORD timeout ) > > 177 { > > 178 WaitForMultipleObjectsEx( 0, NULL, FALSE, timeout, FALSE ); > > 179 } > > > > > > WaitForMultipleObjectsEx() has problems when it gets to 257: > > 256 SERVER_END_REQ; > > 257 if (ret == STATUS_PENDING) ret = wait_reply( &cookie ); > > 258 if (ret != STATUS_USER_APC) break; > > > > ret is 1079729528, btw. > > > > AFAIK, __DTOR_END__ (see near bottom of stack) is the destructor for > > a > > function call in ntdll. I'm probably missing something obvious, but I > > don't see the connection between scheduler/synchro.c:257 and ntdll. > > The > > closest is wait_reply() (in scheduler/client.c) calls wait_reply_data > > (in > > same file), which calls NtCurrentTeb(), which is commented as an > > NTDLL > > function. But there doesn't seem to be an implementation of > > NtCurrentTeb > > in ntdll. > > > > Any ideas? > > > > Cheers, > > > > Paul. > > > > [1] http://www.winehq.com/hypermail/wine-devel/2002/08/0006.html > > [2] http://www.winehq.com/hypermail/wine-devel/2002/07/0386.html > > > > PS, I'll create a bugzilla in a bit. ---- Paul Millar

Sept. 2, 2002

Re: current wine status pr-1

by Paul Millar

Hi Tom, On Mon, 2 Sep 2002, tom wrote: > Paul Millar wrote: > >On Sun, 1 Sep 2002, tom wrote: > >>I have a pre-1 hacked together and request any feed back that you can give. > > > >I'm doing rolling CVS regression/conformance testing and reporting back > >whenever something breaks. How about adding an extra line under the "Wine > >Regression Test Suite"? > > > Hi Paul, > > Is this ** Part ** of the Regression Test Suite or a different > category to add ? It could probably be argued either way ... :) In the limited meaning of Regression Test Suite, then the answer is no. > I am not a developer so please look over me if this > is a dumb > question ... If it is part of the Regression Test Suite I will just add > you in as a worker > with CodeWeavers . Well, I don't claim to have written anything in the Regression Test Suite (only one completely trivial patch), so I'd rather my name wasn't in the "workers" section. > If it is a Different category I think it shold be like this > > Rolling cvs testing > Documentation = > workers = Paul Millar > % = 10% Hmmm, yes. On the whole, I think this is better. You can put me down for Documentation too. I'm not sure what (if any) documentation is really needed, but I think there's a reasonable amount at: http://www.astro.gla.ac.uk/users/paulm/WRT/ and http://www.astro.gla.ac.uk/users/paulm/WRT/help.php Its difficult to gauge a percent-completeness for the rolling regression testing. I'm quite happy with the functionality as it stands now (although I've got a few ideas for improvements). Its been quite stable (apart from some problems with thread deadlocks) for quite a while now, so I'd say its probably around 90% or so. > Is the ( Regression Test Suite ) a program to test the Regression % or > the % of the Regression ? As one is a app the other is a % > If it is a app do you know the current % done ? I don't know if this answers your question, but the Regression Test Suite is a series of explicit statements of what is correct behaviour of the Windows API. Calling function Foo() with parameter "Bar" should return "Baz" : that sort of thing. Information is gleaned from MS's official documentation and from direct testing of various Windows platforms. There's a little more info on the first URL above. Ideally we want all the functions implemented by wine to precisely match the result from Windows under all circumstances (or at least all circumstances where it matters for a program). This behaviour should then be tested to make sure nothing breaks at a later date. For calculating a percentage, the script calculates the number of APIs implemented, and the number of those functions that appears in at least one regression test. The idea is divide one by the other and you have a measure of what percent of wine is tested by the Regression Suite (hence how complete it is). Unfortunate the estimate almost certainly an over-estimate. The calculated number of implemented API is via a crude grep. The estimate also assumes that, just because a function is mentioned in a regression test, the function should be counted as "tested". Both bias towards an increased percentage, so the 10.3% value should be taken with a generous pinch of salt :) Cheers, Paul. ---- Paul Millar

Sept. 2, 2002

Re: Implements shdocvw.101

by Eric Pouech

Sylvain Petreolle a écrit : > > Changelog: > Implements shdocvw.101, which is a call to shlwapi.PathRemoveBackslashW wouldn't a forward in the spec file be more appropriate ? 1+

Sept. 2, 2002

Re: current wine status pr-1

by tom

Dimitrie O. Paun wrote: >On September 1, 2002 07:27 am, tom wrote: > > > >>Known ToDo's will be next on my list after ** WE ** get this up to date.. >> >> > >Having the status done is great, having a list of TODOs (for items that are > > >>70%complete) of what needs to be done to make them 100% complete >> >> >would be fantastic. > >We can enter bugs for these in Bugzilla, and semi-automate the status >tracking this way. This is also a great way to (1) spread the intimate >knowladge that only a few people have about these subsystems, and >(2) focus development and getting more people to help. > > > > Well I was going to ask for what need's to be done in order for Wine to become 1.0.0 ..... But after reading over the last years worth of WWN it seem's everytime this is brought up a nice FLAME WAR starts up . So not to start a flame war just yet ....... should ToDo's be 70%complete) of what needs to be done to make them 100% complete OR What are the ToDo's to make a 1.0.0 release Tom P.S on the part about ( getting more people to help ) Good Luck !! I ask on the user list for help and one guy said he would ...He has not done any thing so far.. And this is a (( non programer )) thing that people can step up and help out on. I guess I could consider this as help as now I only have my own self in my way :)

Sept. 2, 2002

Re: current wine status pr-1

by tom

Paul Millar wrote: >On Sun, 1 Sep 2002, tom wrote: > > >>I have a pre-1 hacked together and request any feed back that you can give. >> >> > >I'm doing rolling CVS regression/conformance testing and reporting back >whenever something breaks. How about adding an extra line under the "Wine >Regression Test Suite"? > Hi Paul, Is this ** Part ** of the Regression Test Suite or a different category to add ? I am not a developer so please look over me if this is a dumb question ... If it is part of the Regression Test Suite I will just add you in as a worker with CodeWeavers . If it is a Different category I think it shold be like this Rolling cvs testing Documentation = workers = Paul Millar % = 10% Is the ( Regression Test Suite ) a program to test the Regression % or the % of the Regression ? As one is a app the other is a % If it is a app do you know the current % done ? Alexandre can you chime in here ? Tom > >Something like the following: > >--- wine-status.txt-old Mon Sep 2 12:30:00 2002 >+++ wine-status.txt Mon Sep 2 12:31:03 2002 >@@ -399,6 +399,7 @@ > Wine Regression Test Suite > Documentation = > workers = CodeWeavers >+Rolling cvs testing = Paul Millar > % = 10% > > ( No-Windows installation issues ) > > >For the percentage value, I've hacked together a quick (and dirty ;) >script for calculating it [attached]. Its says what percentage of >implemented Windows functions are mentioned in at least one >regression/unit/conformance test -- I think this is a reasonable number to >use. 'coz of the quick and dirty nature of the script, it takes a fair >time to run. > >Currently the percentage is around 10.3% > >HTH, > >Paul. > >---- >Paul Millar > >

Sept. 2, 2002

Re: current wine status pr-1

by Dimitrie O. Paun

On September 1, 2002 07:27 am, tom wrote: > Known ToDo's will be next on my list after ** WE ** get this up to date.. Having the status done is great, having a list of TODOs (for items that are >70%complete) of what needs to be done to make them 100% complete would be fantastic. We can enter bugs for these in Bugzilla, and semi-automate the status tracking this way. This is also a great way to (1) spread the intimate knowladge that only a few people have about these subsystems, and (2) focus development and getting more people to help. -- Dimi.

Sept. 2, 2002

Re: current wine status pr-1

by Paul Millar

On Sun, 1 Sep 2002, tom wrote: > I have a pre-1 hacked together and request any feed back that you can give. I'm doing rolling CVS regression/conformance testing and reporting back whenever something breaks. How about adding an extra line under the "Wine Regression Test Suite"? Something like the following: --- wine-status.txt-old Mon Sep 2 12:30:00 2002 +++ wine-status.txt Mon Sep 2 12:31:03 2002 @@ -399,6 +399,7 @@ Wine Regression Test Suite Documentation = workers = CodeWeavers +Rolling cvs testing = Paul Millar % = 10% ( No-Windows installation issues ) For the percentage value, I've hacked together a quick (and dirty ;) script for calculating it [attached]. Its says what percentage of implemented Windows functions are mentioned in at least one regression/unit/conformance test -- I think this is a reasonable number to use. 'coz of the quick and dirty nature of the script, it takes a fair time to run. Currently the percentage is around 10.3% HTH, Paul. ---- Paul Millar

Sept. 2, 2002

Mono / winforms + Winelib

by Steven Edwards

I have started some discussion with the Mono developers on how to better share our work and they have sent these directions for anyone that is interested in testing Mono with Winelib. There is also a Mono build for Win32 if you want to test it under Wine/ReactOS. I will try and find some free time in the next few weeks to see if I can help with documenting problems or areas our projects can work together better. Note: forwarded message attached. __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com

Sept. 2, 2002