April 2002 - Wine-Devel - list.winehq.org

bug in wine install
by Yannick Fillatrau April 26, 2002

April 26, 2002

I just have downloaded the source of wine v. 20020411, I launched ./tools/wineinstall as a normal user and I was told to enter the root password, the install crashed. Here is a sample of stdout: Wine build complete. --- Performing 'make install' as root to install binaries, enter root password Mot de passe: /bin/bash: - : unrecognized option Either you entered an incorrect password or we failed to run 'make install' correctly. If you didn't enter an incorrect password then please report this error to wine-devel(a)winehq.com. Installation failed, aborting. --- I'm sure the password was correct...

2 1

FD_CLOSE, again
by Martin Wilck April 26, 2002

April 26, 2002

I still have problems with FD_CLOSE signalling. AFAICS FD_CLOSE must be signalled when either of the three following conditions hold: 1 Network error (Linux signals POLLERR) 2 Graceful close by the peer (Linux signals POLLHUP) 3 shutdown (SD_SEND) by the peer (Linux signals POLLIN with 0 bytes to read). ** Condition 3 will only be noticed if we tell poll() we're interested ** ** in POLLIN. ** In that case, if 1 or 2 occurs, POLLIN will also be signalled, whether or not there are still data to be read. However, we cannot simply activate POLLIN always, because if there _is_ data to be read on a normal connection and the app does not read it immediately, the server would busy-loop. We can take advantage of the fact that after every recv(), winsock will notify the server and try to re-enable FD_READ. (This does not hold for ReadFile() operations, as I pointed out in my recent "RFC..." posting). Thus what we could do is enable polling for POLLIN whenever FD_READ is re-enabled, even if then app has not registered for FD_READ notification, and disable it when POLLIN is received. Furthermore, finishing an asynchronous read request would also reenable POLLIN, whether or not there are more requests in read queue. Only an app that uses synchronous ReadFile() calls would never see FD_CLOSE. Does that seem correct, or am I again overlooking something?? It is a completely different story _at what time_ FD_CLOSE should be signalled when one ove the above 3 conditions is actually encountered. The Winsock2 spec says different things: In docs of WSAEventSelect: "FD_CLOSE should only be posted after all data is read from a socket, but an application should check for remaining data upon receipt of FD_CLOSE to avoid any possibility of losing data". This suggests that we could signal FD_CLOSE if POLLHUP is received, even if there is still data to be read, although we "should" not. In docs of WSAAsyncSelect: "[FD_CLOSE is posted] after remote system initiated graceful close, when no data currently available to receive (note: if data has been received and is waiting to be read when the remote system initiates a graceful close, the FD_CLOSE is not delivered until all pending data has been read)" This suggests the opposite - signal FD_CLOSE only after the app has read all data, even if this is far later than the actual POLLHUP. Actually this suggests that FD_CLOSE is _equivalent_ with condition 3 above, regardless if 1 or 2 are in effect. This is the behaviour I have tried to implement in my latest patches. Again, am I overlooking something? Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

1 0

RFC: How should ReadFile() on sockets behave ??
by Martin Wilck April 26, 2002

April 26, 2002

If there is a socket for which event notification has been requested by the application with WSAEventSelect(), the behaviour is as follows: - When data arrives, FD_READ is signalled _ONCE_. - FD_READ is only delivered again if the app explicitly reenables it with WSAEventSelect/WSAAsyncSelect or if the application issues a recv() call. - The latter is accomplished in wine by calling _enable_event ( FD_READ, ...) after every recv() operation in the winsock code. - If an app uses ReadFile() rather than a winsock call to retrieve data, the FD_READ event is of course not reenabled, because the current implementation in file.c has no concept of socket events. Question: should ReadFile() behave like recv(), i.e. reenable FD_READ, or not? If yes, we would have a certain dependency of the ReadFile() code on winsock, because FD_READ etc are winsock-specific macros. If no, an app that relies on ReadFile() reenabling FD_READ will obviously fail. The best thing would probably be to do this in the server, but we currently can't, because the server does not notice when a read operation is finished. Opinions? Martin -- Martin Wilck Phone: +49 5251 8 15113 Fujitsu Siemens Computers Fax: +49 5251 8 20409 Heinz-Nixdorf-Ring 1 mailto:Martin.Wilck(a)Fujitsu-Siemens.com D-33106 Paderborn http://www.fujitsu-siemens.com/primergy

2 2

file.c:FILE_ReadFileEx - fd is not overlapped
by Marcelo Welter April 26, 2002

April 26, 2002

Helle friends Still fighting with my serial printers.. :) I upgrade my wine sources today with CVS and more advantages are in this new code (i'm very happy) but with one printer i receive the messages: trace:file:fd is not overlapped i comment the lines //if ( ! (flags & FD_FLAG_OVERLAPPED) ) { // WARN ( "fd is not overlapped\n" ); // SetLastError ( ERROR_INVALID_PARAMETER ); // goto error; //} in files/file.c and my printer communicate good. What i can change in my application to work with serial in this case See in +comm,+file trace:comm:ClearCommError handle 48 cbInQue = 2 cbOutQue = 0 trace:file:ReadFile 48 0x10025308 2 0x40566828 (nil) trace:file:FILE_TimeoutRead 48 0x10025308 2 0x40566828 trace:file:FILE_ReadFileEx file 48 to buf 0x10025308 num 2 0x40566794 func (nil) warn:file:FILE_ReadFileEx fd is not overlapped trace:comm:ClearCommError handle 48 cbInQue = 2 cbOutQue = 0 trace:file:ReadFile 48 0x10025308 2 0x40566828 (nil) trace:file:FILE_TimeoutRead 48 0x10025308 2 0x40566828 trace:file:FILE_ReadFileEx file 48 to buf 0x10025308 num 2 0x40566794 func (nil) warn:file:FILE_ReadFileEx fd is not overlapped Marcelo

2 1

Byte Swapping in storage32.c for solaris
by Warren_Baird＠cimmetry.com April 26, 2002

April 26, 2002

I've been running into some problems with byte swapping in ole related code - it looks like the relevant stuff is in storage32.c - I've modified StorageUtl_{Read,Write}Word and DWord to byteswap on bigendian platforms, and that seems to help, but I'm also running into problems with the wchar property names in StorageImpl_{Read,Write}Property - the individual characters are showing up in the wrong order, so "Data" is showing up as 0x44006100 0x74006100 instead of 0x00440061 0x00740061 as I would expect... Is it safe to use the same approach here? should ReadProperty byteswap each wchar and then WriteProperty byteswap it again? There seem to be a lot of places things like this happen: StorageImpl_ReadProperty(This, propertyIndex, &chainProperty); chainProperty.startingBlock = bbHeadOfChain; StorageImpl_WriteProperty(This, propertyIndex, &chainProperty); and I'm not sure how else to handle these cases... Also - at the moment the only byteswapping macros actually appear in tools/wrc/wrctypes.h - would it make sense to move them to one of the top-level include directories, and use them in both storage32.c and in wrc? If so, which include file should I drop them in? Thanks! Warren

1 0

Bug 572
by Andriy Palamarchuk April 26, 2002

April 26, 2002

Alexandre, could you look at bug 572: http://bugs.codeweavers.com/show_bug.cgi?id=572 It is possible that this bug is caused by your patch. Thanks, Andriy Palamarchuk __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/

2 2

existing cooperation with mono?
by Freddy BL April 26, 2002

April 26, 2002

Hi Wine-Team! Existing cooperations between the Wine-project and the Mono-project (http://www.go-mono.org)? At the moment it seams, that in the future there exists under MS-Windows three types of programs: programs which are in native-code (that can be run on Wine and can be portet to Linux by re-compiling with Wine), programs which are in MS-IL-code (that can in the future be run on Mono I hope) and mixed programs (IL-Code-programs, which integrate Native-Code DLLs and Native-Code-programs, which integrate IL-Code DLLs). And I think, that for the last type of programs a cooperation between the Wine-Devels and the Mono-Devels is very advantageous. So, existing this cooperations? (One of the results of an coopration could be an installer like that by CodeWeavers, which can be install both (Wine and Mono) for example) Greatings Freddy BL _________________________________________________________________ Senden und empfangen Sie Hotmail über Ihr Mobilgerät: http://mobile.msn.com

3 2

[Germany] Linuxtag
by Uwe Bonnes April 26, 2002

April 26, 2002

Hallo, is there anybody beside me willing to care for a booth at Linuxtag June 6-9 in Karlsruhe? Please give feedback so I can apply for a booth. Beside our normal program winex and crossover might be good objects to demonstrate. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

More BUG fixes for winsock2 patch series
by Martin Wilck April 26, 2002

April 26, 2002

Patch: BUGS in my recently submitted patch series This applies over my complete patch series - I will send clean patches tomorrow. The fixes in server/file.c and server/serial.c relate to Rein Klazes' problem. Rein: please tell me if they fix it!! Patch http://www.winehq.com/hypermail/wine-patches/2002/04/0163.html is also needed. Modfied files: dlls/winsock: socket.c (allocation error) server: sock.c (remove socket from select loop for blocking sockets, too) file.c (try to serve async requests immediately) serial.c (dito) diff -ruNX ignore CVS/wine/dlls/winsock/socket.c TMP/wine/dlls/winsock/socket.c --- CVS/wine/dlls/winsock/socket.c Thu Apr 25 20:20:37 2002 +++ TMP/wine/dlls/winsock/socket.c Thu Apr 25 19:46:05 2002 @@ -2479,7 +2479,7 @@ goto error; } - iovec = WS_ALLOC ( dwBufferCount * sizeof (struct iovec) ); + iovec = HeapAlloc (GetProcessHeap(), 0, dwBufferCount * sizeof (struct iovec) ); if ( !iovec ) { diff -ruNX ignore CVS/wine/server/file.c TMP/wine/server/file.c --- CVS/wine/server/file.c Thu Apr 25 20:20:36 2002 +++ TMP/wine/server/file.c Thu Apr 25 20:18:57 2002 @@ -389,6 +389,8 @@ if ( status == STATUS_PENDING ) { + struct pollfd pfd; + if ( !async ) async = create_async ( obj, current, ptr ); if ( !async ) @@ -397,6 +399,15 @@ async->status = STATUS_PENDING; if ( !async->q ) async_insert( q, async ); + + /* Check if the new pending request can be served immediately */ + pfd.fd = obj->fd; + pfd.events = file_get_poll_events ( obj ); + pfd.revents = 0; + poll ( &pfd, 1, 0 ); + + if ( pfd.revents ) + file_poll_event ( obj, pfd.revents ); } else if ( async ) destroy_async ( async ); else set_error ( STATUS_INVALID_PARAMETER ); diff -ruNX ignore CVS/wine/server/serial.c TMP/wine/server/serial.c --- CVS/wine/server/serial.c Thu Apr 25 20:20:36 2002 +++ TMP/wine/server/serial.c Thu Apr 25 20:27:11 2002 @@ -282,6 +282,8 @@ if ( status == STATUS_PENDING ) { + struct pollfd pfd; + if ( !async ) async = create_async ( obj, current, ptr ); if ( !async ) @@ -293,6 +295,19 @@ async_add_timeout(async,timeout); async_insert(q, async); } + + /* Check if the new pending request can be served immediately */ + pfd.fd = obj->fd; + pfd.events = serial_get_poll_events ( obj ); + pfd.revents = 0; + poll ( &pfd, 1, 0 ); + + if ( pfd.revents ) + /* serial_poll_event() calls set_select_events() */ + serial_poll_event ( obj, pfd.revents ); + else + set_select_events ( obj, pfd.events ); + return; } else if ( async ) destroy_async ( async ); else set_error ( STATUS_INVALID_PARAMETER ); diff -ruNX ignore CVS/wine/server/sock.c TMP/wine/server/sock.c --- CVS/wine/server/sock.c Thu Apr 25 20:20:36 2002 +++ TMP/wine/server/sock.c Thu Apr 25 15:10:54 2002 @@ -250,7 +250,6 @@ sock->errors[FD_CONNECT_BIT] = sock_error( sock->obj.fd ); if (debug_level) fprintf(stderr, "socket %d connection failure\n", sock->obj.fd); - set_select_events( &sock->obj, -1 ); } } else if (sock->state & FD_WINE_LISTENING) @@ -269,7 +268,6 @@ sock->pmask |= FD_ACCEPT; sock->errors[FD_ACCEPT_BIT] = sock_error( sock->obj.fd ); sock->hmask |= FD_ACCEPT; - set_select_events( &sock->obj, -1 ); } } else { @@ -335,11 +333,17 @@ if (debug_level) fprintf(stderr, "socket %d aborted by error %d, event: %x - removing from select loop\n", sock->obj.fd, sock->errors[FD_CLOSE_BIT], event); - set_select_events( &sock->obj, -1 ); } } - sock_reselect( sock ); + if ( sock->pmask & FD_CLOSE || event & (POLLERR|POLLHUP) ) + { + if ( debug_level ) + fprintf ( stderr, "removing socket %d from select loop\n", sock->obj.fd ); + set_select_events( &sock->obj, -1 ); + } + else + sock_reselect( sock ); /* wake up anyone waiting for whatever just happened */ if ( sock->pmask & sock->mask || sock->flags & FD_FLAG_OVERLAPPED ) sock_wake_up( sock, event );

3 2

Last header patch for Mingw32 I think (wingdi.h)
by Steven Edwards April 25, 2002

April 25, 2002

cvs diff -u wingdi.h Index: wingdi.h =================================================================== RCS file: /home/wine/wine/include/wingdi.h,v retrieving revision 1.69 diff -u -r1.69 wingdi.h --- wingdi.h 3 Apr 2002 22:08:27 -0000 1.69 +++ wingdi.h 25 Apr 2002 16:48:19 -0000 @@ -24,6 +24,14 @@ extern "C" { #endif +#ifdef __MINGW__ +#undef _MAX_PATH +#undef _MAX_DIR +#undef _MAX_EXT +#undef _MAX_DRIVE +#include "stdlib.h" +#endif + typedef struct _ABCFLOAT { FLOAT abcfA; FLOAT abcfB; "Every revolution was once a thought in one man's mind" - Ralph Waldo Emerson

2 3