I could probably run some tests under WinXP. I just need to compile the
tests on windows, execute them, and post output to wine-devel? Is this correct?
You caught me... I thought something like this existed.
I would say that by default, Auto should be 0.
I think this would be best for the average user.
They are probably even less likely than me to read the
debugging documentation (and want to change a registry
setting like this).
-- Jeff S
>From: Eric Pouech <eric.pouech(a)wanadoo.fr>
>
>>Can we do something like throw up a message box before loading the
>>debugger,
>>asking if we want to debug? Or perhaps there should be a command-line
>>option to
>>the debugger that presents said dialog, then use that option when starting
>>the
>>debugger in the event of an crash.
>RTFM
>hints: AeDebug, Auto
>A+
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
>From: vkxzjq6lg(a)cswebmail.com
>
>Francois Gouget wrote:
>
> > Of course, that implies that we should promptly fix any such crash.
> > Otherwise it just makes Wine unusable without any benefit.
>
>That's the catch. I'm not approaching Wine as a Wine developer. Wine is
>almost ready for
>prime time now and as a non-Wine developer (who's roped in so far only as
>far as necessary
>to get the app I want to run running) I'm approaching it as a near
>production system.
>
>When only hard core Wine developers were seeing it, opening the debugger
>made sense.
>
>Wine is leaving the core development stage and now it's time to be
>arranging for bug
>reporting mechanisms which don't require that you be a programmer willing
>to start
>debugging Wine to get your applications running.
>
>That means avoiding a raw debugger window and providing something more end
>user friendly.
>To me that means something like logging every non-dangerous failure
>possible rather than
>killing the application. Then, when the application finishes, winseerver
>can pop up a
>polite window telling the user that there was a problem and asking them to
>report it to
>the developers, making it easy to do that.
>
>It definitely doesn't involve opening debugger windows. Those will scare
>away the end
>users who need to be submitting those logs so the developers can see which
>app or internal
>routine was breaking the rules and what needs to be fixed.
>
>So: Wine's almost there (and congratulations on getting to the point where
>I can seriously
>write that!). Time to be thinking about what end users can handle and
>changing how garbage
>data reporting is handled to make it more friendly to them.
Can we do something like throw up a message box before loading the debugger,
asking if we want to debug? Or perhaps there should be a command-line
option to
the debugger that presents said dialog, then use that option when starting
the
debugger in the event of an crash.
Perhaps this can be combined with some of the other ideas to create a
reasonable
user experience during a failure.
-- Jeff S
_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
"Dimitrie O. Paun" wrote:
>
> On December 5, 2002 11:16 am, Alexandre Julliard wrote:
> > It's the kind of thinking that leads to having an exception
> > handler inside strlen() like Windows does. It's just plain wrong.
>
> <nod/>. This is generally true for other things as well:
>
> 1. Many places in our code where we have invariant like
> pointer p is never NULL, yet we always have:
>
> if (!p) return NULL; /* or whatever error condition */
>
> Such a check is harmful (hides bugs), slow (useless
> runtime check), bloat (more generated code),
> ugly (clutters the code), at the very least. Just
> Don't Do It (TM) -- let the code crash.
Agreed that it's harmful because it hides what may be a real error. Lousy
idea unless p really is allowed to have that value.
If it's a call exposed to external callers it needs to warn somehow, even to
the console if necessary (assuming that Wine wants to give end users some
feedback they can give back to the Wine developers and to the developer of
the faulty application). Those warnings can vanish should there ever be a
production build with debugging removed. If it's internal only it should be
an assert or fixme.
Being too free with "let the code crash" is a bad idea. Microsoft got a lot
of really bad heckling in the Windows 3.1 era for GPFs. Wine doesn't want to
crash if it's reasonably harmless to continue (like for a failed screen
update). Does want to report the problem, of course, rather than silently
ignore it, otherwise it'll never get fixed.
>
> 2. ZeroMemory when we don't need to, when we pass struct
> internally, yet same functions can be called externally
> with no guarantee that the struct has unused field
> zeroed out.
>
Agreed if it is a call to an internal only function. If it's to a function
with an external API then it may need zeroing to get to the state required
for that.
> 3. In general, we have all sort of 'defensive programming'
> checks for invariants. Problem is, we never going to
> catch bugs in this area this way. Just use assert()
> if you feel a check is needed.
If it's a documented external interface it can't assert and die because the
application making the call presumably works on real Windows. So it needs to
be warned/fixme'd or whatever so end users can report the issue to Wine
developers for fixing. If it's internal, assert is sort of OK, though as
someone trying to get an application working I want a fixme rather than
sudden death (except in file output interfaces!). I don't need perfect
functionality. I do need to get the app to the point where it is safely
functioning and an assert may kill it when it doesn't need to die.
> In short, this defensive programming crap is just that: crap.
Do you agree with the way I've explained how I see the difference between
redundant defensive programming and detecting and reporting problems which
need to be fixed? If not, where do you differ and why?
James
___________________________________________________
The ALL NEW CS2000 from CompuServe
Better! Faster! More Powerful!
250 FREE hours! Sign-on Now!
http://www.compuserve.com/trycsrv/cs2000/webmail/
Hey, looks like the Samba guys are doing
a registry editor...
- Dan
-------- Original Message --------
Subject: A registry editor taking shape ...
Date: Mon, 9 Dec 2002 01:56:50 -0800 (PST)
From: Richard Sharpe <rsharpe(a)richardsharpe.com>
To: <samba-technical(a)samba.org>
Hi,
A registry editor, editreg, is slowly taking shape in Samba-head.
The goal is to be able to do things like:
- delete keys and values
- add keys and values
- change keys and values
- Change the SIDS/SecDescs applied to keys.
- write out the changes tree
- create a tree from scratch
What would be useful is some thoughts on how the interface should be
constructed, as in command-line, or a .reg file of commands, etc.
Regards
-----
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com
Hola,
Just wondering if you were still doing the import lib stuff. I saw in a past message that you had
some patches outstanding and assumed import lib patch is one of them. I think this is the only
thing holding up being able to compile all of the regression tests under windows via Mingw.
Thanks
Steven
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Hi,
My Results using the batch file and Windows XP. If you need any more
information about msvcrt_test crash, just ask.
My desktop also becomes smaller after running user32_test sysparams, the
approximate time of this is marked below in the appropriate section.
These results are obtained with Windows XP Home
==== advapi32_test ====
h:\wine\wine\dlls\advapi32\tests\registry.c:80: Test failed: data_count
set to 24 instead of 7
h:\wine\wine\dlls\advapi32\tests\registry.c:81: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:94: Test failed: data_count
set to 24 instead of 7
h:\wine\wine\dlls\advapi32\tests\registry.c:95: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:96: Test failed: value set
to 'xxxxxxxxxx' instead of 'Te'
h:\wine\wine\dlls\advapi32\tests\registry.c:97: Test failed: data set to
'xxxxxxxxxx' instead of 'foobar'
h:\wine\wine\dlls\advapi32\tests\registry.c:108: Test failed: data_count
set to24 instead of 7
h:\wine\wine\dlls\advapi32\tests\registry.c:109: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:111: Test failed: data set
to 'xxxxxxxxxx' instead of 'foobar'
h:\wine\wine\dlls\advapi32\tests\registry.c:122: Test failed: data_count
set to24 instead of 7
h:\wine\wine\dlls\advapi32\tests\registry.c:123: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:134: Test failed: expected
ERROR_SUCCESS, got 234
h:\wine\wine\dlls\advapi32\tests\registry.c:135: Test failed: val_count
set to 20 instead of 4
h:\wine\wine\dlls\advapi32\tests\registry.c:136: Test failed: data_count
set to 24 instead of 7
h:\wine\wine\dlls\advapi32\tests\registry.c:137: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:138: Test failed: value is
'xxxxxxxxxx' instead of Test
h:\wine\wine\dlls\advapi32\tests\registry.c:139: Test failed: data is
'xxxxxxxxxx' instead of foobar
h:\wine\wine\dlls\advapi32\tests\registry.c:155: Test failed: data_count
set to 48 instead of 7*sizeof(WCHAR)
h:\wine\wine\dlls\advapi32\tests\registry.c:156: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:169: Test failed: data_count
set to 48 instead of 7*sizeof(WCHAR)
h:\wine\wine\dlls\advapi32\tests\registry.c:170: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:182: Test failed: val_count
set to 5 instead of 4
h:\wine\wine\dlls\advapi32\tests\registry.c:183: Test failed: data_count
set to 48 instead of 7*sizeof(WCHAR)
h:\wine\wine\dlls\advapi32\tests\registry.c:184: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:185: Test failed: value is
not 'Test'
h:\wine\wine\dlls\advapi32\tests\registry.c:195: Test failed: expected
ERROR_SUCCESS, got 234
h:\wine\wine\dlls\advapi32\tests\registry.c:196: Test failed: val_count
set to 5 instead of 4
h:\wine\wine\dlls\advapi32\tests\registry.c:197: Test failed: data_count
set to 48 instead of 7*sizeof(WCHAR)
h:\wine\wine\dlls\advapi32\tests\registry.c:198: Test failed: type 2 is
not REG_SZ
h:\wine\wine\dlls\advapi32\tests\registry.c:199: Test failed: value is
not 'Test'
h:\wine\wine\dlls\advapi32\tests\registry.c:200: Test failed: data is
not 'foobar'
registry: 56 tests executed, 0 marked as todo, 31 failures.
==== kernel32_test ====
alloc: 58 tests executed, 0 marked as todo, 0 failures.
atom: 229398 tests executed, 0 marked as todo, 0 failures.
codepage: 2 tests executed, 0 marked as todo, 0 failures.
directory: 48 tests executed, 0 marked as todo, 0 failures.
drive: 156 tests executed, 0 marked as todo, 0 failures.
environ: 39 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\kernel\tests\file.c:578: Test failed: DeleteFile
should fail with an empty path, and last error value should be
ERROR_FILE_NOT_FOUND
h:\wine\wine\dlls\kernel\tests\file.c:610:Current offset = 0015
h:\wine\wine\dlls\kernel\tests\file.c:635:Current offset = 0015
file: 487238 tests executed, 0 marked as todo, 1 failure.
format_msg: 58 tests executed, 0 marked as todo, 0 failures.
generated: 609 tests executed, 0 marked as todo, 0 failures.
locale: 54 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\kernel\tests\path.c:927:TMP=C:\WINDOWS\TEMP
h:\wine\wine\dlls\kernel\tests\path.c:935:TMP=C:\WINDOWS
h:\wine\wine\dlls\kernel\tests\path.c:944:TMP=C:\
h:\wine\wine\dlls\kernel\tests\path.c:954:TMP=C:
h:\wine\wine\dlls\kernel\tests\path.c:879: Test failed: win2000 BUG:
expected 12, got 13
h:\wine\wine\dlls\kernel\tests\path.c:892: Test failed: win2000 BUG:
expected 12, got 13
h:\wine\wine\dlls\kernel\tests\path.c:898: Test failed: win2000 BUG:
should return path without terminating back slash
path: 2083 tests executed, 0 marked as todo, 3 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\kernel\tests\process.c:374: Test failed:
StartupInfoA:lpDesktop expected (null), got WinSta0\Default
h:\wine\wine\dlls\kernel\tests\process.c:375: Test failed:
StartupInfoA:lpTitle expected (null), got
C:\DOCUME~1\Owner\DESKTOP\WINETE~1\KERNEL32_TEST.exe
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\kernel\tests\process.c:450: Test failed:
StartupInfoA:lpDesktop expected (null), got WinSta0\Default
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\kernel\tests\process.c:527: Test failed:
StartupInfoA:lpTitle expected (null), got
C:\DOCUME~1\Owner\DESKTOP\WINETE~1\KERNEL32_TEST.exe
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
tests/process.c: 1 tests executed, 0 marked as todo, 0 failures.
process: 116 tests executed, 0 marked as todo, 4 failures.
thread: 112 tests executed, 0 marked as todo, 0 failures.
==== msvcrt_test ====
Fails to run (msvcrt_test.exe has encountered a problem and needs to
close. We are sorry for the inconvenience)
Debug Shows Unhandled exception in msvcrt_test.exe (NTDLL.DLL):
0xC0000005: Access Violation
More information available if required
==== netapi32_test ====
h:\wine\wine\dlls\netapi32\tests\access.c:95: Test failed: Bad Network
Path
access: 23 tests executed, 0 marked as todo, 1 failure.
apibuf: 15 tests executed, 0 marked as todo, 0 failures.
wksta: 14 tests executed, 0 marked as todo, 0 failures.
==== rpcrt4_test ====
h:\wine\wine\dlls\rpcrt4\tests\rpc.c:124: ** Uuid Conversion and
Comparison Tests **
rpc: 901 tests executed, 0 marked as todo, 0 failures.
==== shell32_test ====
generated: 272 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\shell32\tests\shlfileop.c:286: Test failed: Files are
copied to other directory
h:\wine\wine\dlls\shell32\tests\shlfileop.c:287: Test failed: The file
is copied
shlfileop: 121 tests executed, 0 marked as todo, 2 failures.
==== shlwapi_test ====
h:\wine\wine\dlls\shlwapi\tests\clist.c:367: Test failed: allowed bad
element size
h:\wine\wine\dlls\shlwapi\tests\clist.c:372: Test failed: allowed adding
a container
clist: 236 tests executed, 0 marked as todo, 2 failures.
generated: 19 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\shlwapi\tests\shreg.c:172: Test failed: (44,43)
h:\wine\wine\dlls\shlwapi\tests\shreg.c:196: Test failed: (44,43)
h:\wine\wine\dlls\shlwapi\tests\shreg.c:206: Test failed: ()
h:\wine\wine\dlls\shlwapi\tests\shreg.c:207: Test failed: ()
h:\wine\wine\dlls\shlwapi\tests\shreg.c:208: Test failed: (44,43)
h:\wine\wine\dlls\shlwapi\tests\shreg.c:219: Test failed: (44,43)
h:\wine\wine\dlls\shlwapi\tests\shreg.c:241: Test failed: didn't open
dest
shreg: 39 tests executed, 0 marked as todo, 7 failures.
==== user32_test ====
class: 80 tests executed, 0 marked as todo, 0 failures.
generated: 1524 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\user\tests\sysparams.c:184:testing SPI_{GET,SET}BEEP
h:\wine\wine\dlls\user\tests\sysparams.c:306:testing SPI_{GET,SET}MOUSE
h:\wine\wine\dlls\user\tests\sysparams.c:374:testing SPI_{GET,SET}BORDER
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=BorderWidth,
testValue=1, value=
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=BorderWidth,
testValue=0, value=
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=BorderWidth,
testValue=7, value=
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=BorderWidth,
testValue=20, value=
h:\wine\wine\dlls\user\tests\sysparams.c:406:testing
SPI_{GET,SET}KEYBOARDSPEED
h:\wine\wine\dlls\user\tests\sysparams.c:440:testing
SPI_ICONHORIZONTALSPACING
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=IconSpacing,
testValue=101, value=
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=IconSpacing,
testValue=32, value=
h:\wine\wine\dlls\user\tests\sysparams.c:480:testing
SPI_{GET,SET}SCREENSAVETIMEOUT
h:\wine\wine\dlls\user\tests\sysparams.c:515:testing
SPI_{GET,SET}SCREENSAVEACTIVE
h:\wine\wine\dlls\user\tests\sysparams.c:555:testing
SPI_{GET,SET}KEYBOARDDELAY
h:\wine\wine\dlls\user\tests\sysparams.c:590:testing
SPI_ICONVERTICALSPACING
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=IconVerticalSpacing,
testValue=101, value=
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=IconVerticalSpacing,
testValue=32, value=
h:\wine\wine\dlls\user\tests\sysparams.c:635:testing
SPI_{GET,SET}ICONTITLEWRAP
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=IconTitleWrap,
testValue=1, value=
h:\wine\wine\dlls\user\tests\sysparams.c:170: Test failed: Wrong value
in registry: subKey=Control Panel\Desktop, valName=IconTitleWrap,
testValue=0, value=
h:\wine\wine\dlls\user\tests\sysparams.c:670:testing
SPI_{GET,SET}MENUDROPALIGNMENT
h:\wine\wine\dlls\user\tests\sysparams.c:707:testing
SPI_SETDOUBLECLKWIDTH
h:\wine\wine\dlls\user\tests\sysparams.c:738:testing
SPI_SETDOUBLECLKHEIGHT
h:\wine\wine\dlls\user\tests\sysparams.c:770:testing
SPI_SETDOUBLECLICKTIME
h:\wine\wine\dlls\user\tests\sysparams.c:817:testing
SPI_SETMOUSEBUTTONSWAP
// Desktop Resizes somewhere between here:
h:\wine\wine\dlls\user\tests\sysparams.c:880:testing
SPI_{GET,SET}DRAGFULLWINDOWS
h:\wine\wine\dlls\user\tests\sysparams.c:915:testing
SPI_{GET,SET}WORKAREA
And Here //
h:\wine\wine\dlls\user\tests\sysparams.c:953:testing
SPI_{GET,SET}SHOWSOUNDS
h:\wine\wine\dlls\user\tests\sysparams.c:997:testing
SPI_{GET,SET}DESKWALLPAPER
sysparams: 318 tests executed, 0 marked as todo, 10 failures.
win: 373 tests executed, 0 marked as todo, 0 failures.
wsprintf: 4 tests executed, 0 marked as todo, 0 failures.
==== wininet_test ====
generated: 252 tests executed, 0 marked as todo, 0 failures.
h:\wine\wine\dlls\wininet\tests\http.c:90:Starting with flags 0x10000000
h:\wine\wine\dlls\wininet\tests\http.c:92:InternetOpenA <--
h:\wine\wine\dlls\wininet\tests\http.c:95:InternetOpenA -->
h:\wine\wine\dlls\wininet\tests\http.c:101:InternetConnectA <--
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0004 0xdeadbeef
INTERNET_STATUS_HANDLE_CREATED(60) 0012E990 4
h:\wine\wine\dlls\wininet\tests\http.c:104:InternetConnectA -->
h:\wine\wine\dlls\wininet\tests\http.c:108:HttpOpenRequestA <--
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbead
INTERNET_STATUS_HANDLE_CREATED(60) 0012EC04 4
h:\wine\wine\dlls\wininet\tests\http.c:122:HttpOpenRequestA -->
h:\wine\wine\dlls\wininet\tests\http.c:126:HttpSendRequestA -->
h:\wine\wine\dlls\wininet\tests\http.c:133:HttpSendRequestA <--
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_RESOLVING_NAME(10) 00D6FB04 15
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_NAME_RESOLVED(11) 00D6FAF4 12
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CONNECTING_TO_SERVER(20) 00D6FB9C 12
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CONNECTED_TO_SERVER(21) 00D6FD40 12
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_SENDING_REQUEST(30) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_REQUEST_SENT(31) 00D6FCE0 4
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_RECEIVING_RESPONSE(40) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_RESPONSE_RECEIVED(41) 00D6FD60 4
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_REQUEST_COMPLETE(100) 00D6FDA8 8
h:\wine\wine\dlls\wininet\tests\http.c:140:Option 0x17 -> 1 8
h:\wine\wine\dlls\wininet\tests\http.c:144:Option 0x22 -> 1
http://www.winehq.com/about/
h:\wine\wine\dlls\wininet\tests\http.c:149:Option 0x16 -> 1 HTTP/1.0
200 OK
Date: Mon, 09 Dec 2002 22:47:48 GMT
Server: Apache/1.3.22 (Unix) (Red-Hat/Linux) mod_ssl/2.8.5
OpenSSL/0.9.6 PHP/4.
1.2
X-Powered-By: PHP/4.1.2
Content-Type: text/html
X-Cache: MISS from cache.net2000.com.au
Connection: close
h:\wine\wine\dlls\wininet\tests\http.c:154:Option 0x22 -> 1
http://www.winehq.com/about/
h:\wine\wine\dlls\wininet\tests\http.c:158:Option 0x5 -> 0
http://www.winehq.com/about/ (12150)
h:\wine\wine\dlls\wininet\tests\http.c:163:Option 0x1 -> 1 text/html
h:\wine\wine\dlls\wininet\tests\http.c:166:Entery Query loop
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 773
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 465
h:\wine\wine\dlls\wininet\tests\http.c:172: Test failed:
InternetQueryDataAvailable failed
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_REQUEST_COMPLETE(100) 00D6FDA8 8
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CLOSING_CONNECTION(50) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CONNECTION_CLOSED(51) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef
INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4
h:\wine\wine\dlls\wininet\tests\http.c:90:Starting with flags 0x0
h:\wine\wine\dlls\wininet\tests\http.c:92:InternetOpenA <--
h:\wine\wine\dlls\wininet\tests\http.c:95:InternetOpenA -->
h:\wine\wine\dlls\wininet\tests\http.c:101:InternetConnectA <--
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0004 0xdeadbeef
INTERNET_STATUS_HANDLE_CREATED(60) 0012E990 4
h:\wine\wine\dlls\wininet\tests\http.c:104:InternetConnectA -->
h:\wine\wine\dlls\wininet\tests\http.c:108:HttpOpenRequestA <--
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbead
INTERNET_STATUS_HANDLE_CREATED(60) 0012EC04 4
h:\wine\wine\dlls\wininet\tests\http.c:122:HttpOpenRequestA -->
h:\wine\wine\dlls\wininet\tests\http.c:126:HttpSendRequestA -->
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CONNECTING_TO_SERVER(20) 0012EA3C 12
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CONNECTED_TO_SERVER(21) 0012EA18 12
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_SENDING_REQUEST(30) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_REQUEST_SENT(31) 0012EB28 4
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_RECEIVING_RESPONSE(40) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_RESPONSE_RECEIVED(41) 0012EB10 4
h:\wine\wine\dlls\wininet\tests\http.c:133:HttpSendRequestA <--
h:\wine\wine\dlls\wininet\tests\http.c:140:Option 0x17 -> 1 8
h:\wine\wine\dlls\wininet\tests\http.c:144:Option 0x22 -> 1
http://www.winehq.com/about/
h:\wine\wine\dlls\wininet\tests\http.c:149:Option 0x16 -> 1 HTTP/1.0
200 OK
Date: Mon, 09 Dec 2002 22:47:49 GMT
Server: Apache/1.3.22 (Unix) (Red-Hat/Linux) mod_ssl/2.8.5
OpenSSL/0.9.6 PHP/4.
1.2
X-Powered-By: PHP/4.1.2
Content-Type: text/html
X-Cache: MISS from cache.net2000.com.au
Connection: close
h:\wine\wine\dlls\wininet\tests\http.c:154:Option 0x22 -> 1
http://www.winehq.com/about/
h:\wine\wine\dlls\wininet\tests\http.c:158:Option 0x5 -> 0
http://www.winehq.com/about/ (12150)
h:\wine\wine\dlls\wininet\tests\http.c:163:Option 0x1 -> 1 text/html
h:\wine\wine\dlls\wininet\tests\http.c:166:Entery Query loop
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 773
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 465
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 1460
h:\wine\wine\dlls\wininet\tests\http.c:183:ReadFile -> 1 447
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CLOSING_CONNECTION(50) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_CONNECTION_CLOSED(51) 00000000 0
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC000C 0xdeadbead
INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4
h:\wine\wine\dlls\wininet\tests\http.c:78:Callback 00CC0008 0xdeadbeef
INTERNET_STATUS_HANDLE_CLOSING(70) 0012EC30 4
http: 28 tests executed, 0 marked as todo, 1 failure.
==== winmm_test ====
h:\wine\wine\dlls\winmm\tests\wave.c:56:found 1 WaveOut devices
h:\wine\wine\dlls\winmm\tests\wave.c:82: 0: "SB Live! Wave Device" 5.10
(1:100): channels=65535 formats=bffff support=002c
h:\wine\wine\dlls\winmm\tests\wave.c:133:Testing invalid 2MHz format
wave: 53 tests executed, 0 marked as todo, 0 failures.
==== ws2_32_test ====
sock: 128 tests executed, 0 marked as todo, 0 failures.
Francois Gouget wrote:
> Of course, that implies that we should promptly fix any such crash.
> Otherwise it just makes Wine unusable without any benefit.
That's the catch. I'm not approaching Wine as a Wine developer. Wine is almost ready for
prime time now and as a non-Wine developer (who's roped in so far only as far as necessary
to get the app I want to run running) I'm approaching it as a near production system.
When only hard core Wine developers were seeing it, opening the debugger made sense.
Wine is leaving the core development stage and now it's time to be arranging for bug
reporting mechanisms which don't require that you be a programmer willing to start
debugging Wine to get your applications running.
That means avoiding a raw debugger window and providing something more end user friendly.
To me that means something like logging every non-dangerous failure possible rather than
killing the application. Then, when the application finishes, winseerver can pop up a
polite window telling the user that there was a problem and asking them to report it to
the developers, making it easy to do that.
It definitely doesn't involve opening debugger windows. Those will scare away the end
users who need to be submitting those logs so the developers can see which app or internal
routine was breaking the rules and what needs to be fixed.
So: Wine's almost there (and congratulations on getting to the point where I can seriously
write that!). Time to be thinking about what end users can handle and changing how garbage
data reporting is handled to make it more friendly to them.
___________________________________________________
The ALL NEW CS2000 from CompuServe
Better! Faster! More Powerful!
250 FREE hours! Sign-on Now!
http://www.compuserve.com/trycsrv/cs2000/webmail/