- Wine-Devel - list.winehq.org

Re: winmm GetDevCaps better pointer check patch
by Robert Shearman June 8, 2004

June 8, 2004

On Sun, 2004-06-06 at 19:26, Robert Reif wrote: > Not a real program but Microsoft's API checking programs do > try non NULL bad pointers and expect an error return rather > than a program crash. > > Are you saying checking a good pointer can cause problems? No, checking a bad pointer can cause problems. See: http://blogs.msdn.com/LarryOsterman/archive/2004/05/18/134471.aspx Rob

4 4

Re: (Still) problem on AMD64 with wine CVS
by Maurizio Monge June 8, 2004

June 8, 2004

> Maurizio, > Ignore what it says in the source, in dlls/ntdlls/virtual.c you can change > the value in ADDRESS_SPACE_LIMIT to suit yourself. Many applications (I > venture to say most ) work fine and my solaris distro has been compiled > like this for two years with few (Actually no) complaints. > > Just don't tell Aleandre, the comment in there about not being able to > change it was directed squarely at me as a result of me doing it ! Stil, it > made wine work, while without changing the define Wine definitely would NOT > > Bob mh, i have set ADDRESS_SPACE_LIMIT to 0xffffffff and i am getting the same error... :-( Does anyone have an idea of why the mmap at the and of the "strace" i posted some time ago fails? Thx Maurizio please CC to monge(at)sns(dot)it

1 0

RE: Incoming Msg
by Twickline June 8, 2004

June 8, 2004

1 0

wine problem
by mguyard June 8, 2004

June 8, 2004

Hello I do that Before starting to work on a big project you may want to try to port a small application. The winemine application from the Wine source tree suits well for testing purposes. It can be found in the programs subdirectory. winemine is a simple application, but has a few C, header and resource files. Run make clean in the winemine source directory if it contains results of previous builds. Create a separate directory with name winemine2, so it won't conflict with the Wine copy of the application. Copy the sources of winemine (files *.c, *.h, *.rc) to this directory. Now run the commands, mentioned above from the winemine2 directory: $ winemaker --lower-uppercase . without any problem and after i go at wine directory and do ./configure and after i type make and i have a lot of errors: dialog.c:64: « p_board » non déclaré (première utilisation dans cette fonction) dialog.c:64: erreur d'analyse syntaxique avant le jeton « ) » dialog.c:65: « hDlg » non déclaré (première utilisation dans cette fonction) dialog.c:67: « TRUE » non déclaré (première utilisation dans cette fonction) dialog.c:69: « WM_COMMAND » non déclaré (première utilisation dans cette fonction) dialog.c:70: « wParam » non déclaré (première utilisation dans cette fonction) dialog.c:71: « IDOK » non déclaré (première utilisation dans cette fonction) dialog.c:78: « IDCANCEL » non déclaré (première utilisation dans cette fonction) dialog.c:84: « FALSE » non déclaré (première utilisation dans cette fonction) dialog.c: Au niveau supérieur: dialog.c:87: erreur d'analyse syntaxique avant « CALLBACK » dialog.c:87: erreur d'analyse syntaxique avant « hDlg » dialog.c: Dans la fonction « TimesDlgProc »: dialog.c:89: erreur de syntaxes avant le jeton « * » dialog.c:92: « uMsg » non déclaré (première utilisation dans cette fonction) dialog.c:93: « WM_INITDIALOG » non déclaré (première utilisation dans cette fonction) dialog.c:94: « p_board » non déclaré (première utilisation dans cette fonction) dialog.c:94: erreur d'analyse syntaxique avant le jeton « ) » dialog.c:98: « hDlg » non déclaré (première utilisation dans cette fonction) dialog.c:102: « FALSE » non déclaré (première utilisation dans cette fonction) dialog.c:103: « TRUE » non déclaré (première utilisation dans cette fonction) dialog.c:105: « WM_COMMAND » non déclaré (première utilisation dans cette fonction) dialog.c:106: « wParam » non déclaré (première utilisation dans cette fonction) dialog.c:107: « IDOK » non déclaré (première utilisation dans cette fonction) dialog.c:108: « IDCANCEL » non déclaré (première utilisation dans cette fonction) dialog.c: Au niveau supérieur: dialog.c:117: erreur d'analyse syntaxique avant « CALLBACK » dialog.c:117: erreur d'analyse syntaxique avant « hDlg » dialog.c: Dans la fonction « AboutDlgProc »: dialog.c:119: « uMsg » non déclaré (première utilisation dans cette fonction) dialog.c:120: « WM_INITDIALOG » non déclaré (première utilisation dans cette fonction) dialog.c:121: « TRUE » non déclaré (première utilisation dans cette fonction) dialog.c:123: « WM_COMMAND » non déclaré (première utilisation dans cette fonction) dialog.c:124: « wParam » non déclaré (première utilisation dans cette fonction) dialog.c:125: « IDOK » non déclaré (première utilisation dans cette fonction) dialog.c:126: « IDCANCEL » non déclaré (première utilisation dans cette fonction) dialog.c:127: « hDlg » non déclaré (première utilisation dans cette fonction) dialog.c:132: « FALSE » non déclaré (première utilisation dans cette fonction) something is not declared so i follow the operation procedure: You are done! Now you can start the application as ./winemine2. If you come across problems preparing and building this application this probably means that winemaker utility is broken by some changes in Wine. Try asking for help on <wine-devel(a)winehq.org> so i try to ask the question at your business. Please help me regards Mickael GUYARD INTA engineer Paris Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

1 0

Re: Spin Counts For Critical Sections on SMP
by Robert Shearman June 8, 2004

June 8, 2004

On Mon, 2004-06-07 at 18:14, Robert Shearman wrote: > Changelog: > Honour spin count setting for critical sections on SMP Actually, this patch isn't right. Don't apply. Rob

1 0

Blizzard Updater Problem
by Erich Hoover June 8, 2004

June 8, 2004

I haven't been able to get the blizzard updater to run on recent versions of wine (I've downloaded from CVS to make sure there isn't a fix). I'm not sure if this is something wrong with my setup or a bug with wine (i recently reinstalled my system with Fedora Core 2 and am no-longer running the same version of wine). I'm executing programs with "setarch i386 wine <appname>" but the blizzard updater seems hosed (though Diablo II and Warcraft III run fine). It appears that the updater doesn't launch correctly (i'm guessing because of the setarch stuff) so I run the updater manually by typing "setarch i386 wine BNupdate.exe" and I get this: fixme:msvcrt:_XcptFilter (-1073741819,0x5584f76c)semi-stub wine: Unhandled exception (thread 0009), starting debugger... fixme:console:SetConsoleCtrlHandler (0x55609ec4,1) - no error checking or testing yet WineDbg starting on pid 0x8 Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x558fc91c). In 32 bit mode. 0x558fc91c: movl $0x0,0x0(%eax) Wine-dbg>quit WineDbg terminated on pid 0x8 At which point I have to type quit to close the debugger (as you can see). Any help would be greatly appreciated, if you need more information just send me a message.

4 7

Warning about ultra-confusing thing
by Mike Hearn June 7, 2004

June 7, 2004

Hi all, Sometimes it is convenient to do a "killall -9 wine-pthread" to kill Wine for whatever reason. This no longer works: $ ps ax | grep wine-pthread | grep -v grep 10425 pts/4 S 0:00 /opt/wine/bin/wine-pthread notepad.exe $ killall wine-pthread wine-pthread: no process killed $ killall wine-preloader $ Huh? WTF is going on here? Well, it seems that "ps" and "killall" look at different places to get the process name, so despite the fact that it appears as wine-pthread in the process list, you must use the name wine-preloader in order to send it signals from the command line. There are reasons for this, which will hopefully become clear when I submit my docs on the Wine init process. For now, you have been warned. thanks -mike

1 0

Re: KERNEL32: implement SetFilePointerEx
by Dmitry Timoshkov June 7, 2004

June 7, 2004

"Mike McCormack" <mike(a)codeweavers.com> wrote: > /*********************************************************************** > + * SetFilePointerEx (KERNEL32.@) > + */ > +BOOL WINAPI SetFilePointerEx( HANDLE hFile, LARGE_INTEGER distance, > + LARGE_INTEGER *newpos, DWORD method ) > +{ > + static const int whence[3] = { SEEK_SET, SEEK_CUR, SEEK_END }; > + BOOL ret = FALSE; > + NTSTATUS status; > + int fd; > + > + TRACE("handle %p offset %lld newpos %p origin %ld\n", > + hFile, distance.QuadPart, newpos, method ); %lld is not portable, Alexandre added wine_dbgstr_longlong() for that purpose. MSDN states that newpos parameter is allowed to be NULL, in that case a new file pointer is not returned. To avoid code duplication SetFilePointer should become just a wrapper for SetFilePointerEx. -- Dmitry.

1 0

Re: winmm GetDevCaps better pointer check patch
by Robert Shearman June 6, 2004

June 6, 2004

On Sun, 2004-06-06 at 17:27, Robert Reif wrote: > Do better check on pointers to memory to be written to. ... ________________________________________________________________________ > + if (IsBadWritePtr(lpCaps, uSize)) ... Does a program depend on these checks? We should only put them in when a program depends on them because they can silently corrupt memory and cause a few other hard to detect side effects. Rob

1 0

Re: fix for launching unix executables
by Andreas Mohr June 6, 2004

June 6, 2004

Hi, On Fri, Jun 04, 2004 at 03:25:00PM +0200, Rein Klazes wrote: > Changelog: > dlls/kernel : process.c > Fix a crash when launching Unix executables. Is there any way to have a test for that in the test suite? Sure hurts to see such quite basic stuff non-working. Andreas Mohr

3 3