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

Re: Crash in BeginPaint running Sams Photofact index, a free VB app
by Uwe Bonnes April 28, 2003

April 28, 2003

>>>>> "Dmitry" == Dmitry Timoshkov <dmitry(a)baikal.ru> writes: Dmitry> "Dan Kegel" <dank(a)kegel.com> wrote: >> Backtrace: =>0 0x409e5873 (BeginPaint+0x9f(hwnd=0x10029, lps=0x0) >> [painting.c:200] in user32.dll.so) (ebp=40892bc4) Dmitry> Attached patch should help a bit. Dmitry> -- Dmitry. Protect BeginPaint and EndPaint from lps being NULL. Dmitry> --- cvs/hq/wine/dlls/user/painting.c Thu Jan 09 03:41:30 2003 Dmitry> +++ painting.c Mon Apr 28 10:15:46 2003 @@ -159,6 +159,8 @@ HWND Dmitry> full_handle; WND *wndPtr; Dmitry> + if (!lps) return 0; + if (!(full_handle = WIN_IsCurrentThread( Dmitry> hwnd ))) { if (IsWindow(hwnd)) @@ -239,6 +241,8 @@ */ BOOL Dmitry> WINAPI EndPaint( HWND hwnd, const PAINTSTRUCT *lps ) { + if Dmitry> (!lps) return FALSE; + ReleaseDC( hwnd, lps->hdc ); ShowCaret( Dmitry> hwnd ); return TRUE; Is lps==NULL an argument that BeginPaint() and EndPaint() should cope with or is it a result for errors hidden deeper? -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

5 7

WineHQ: different pages with same content
by Stefan Leichter April 28, 2003

April 28, 2003

Hello, during browsing WineHQ offline (via wwwoffle) i noticed that the links in the left column of the current WWN are different to the links on the main page and some other (have not tested all) e.g. in the development section of the WWN the CVS link is: http://www.winehq.com/index.php?page=cvs on the main page (and other) the link is http://www.winehq.com/?page=cvs Any reason for this? Bye Stefan

2 1

Re: Patch to get Borland's bcc 5.5 (free beer compiler) to work
by Uwe Bonnes April 28, 2003

April 28, 2003

>>>>> "Troy" == Troy Rollo <wine(a)troy.rollo.name> writes: Troy> The only problem in the head code appears to be in the linker, Troy> which it turns out has a problem when it's told there's 3GB of Troy> user address space. Since Windows only offers a 3GB user address Troy> space in what passes for Microsoft's high end server editions of Troy> the operating system, it is unlikely that this is necessary. My Troy> solution is to drop the user address space to 2GB - if 3GB is Troy> desired, it probably should be a configurable option rather than Troy> hard coded as is the case now. Troy> I dealt with a related FIXME along the way. Troy> diff -u -r1.4 virtual.c --- dlls/ntdll/virtual.c 7 Jan 2003 Troy> 20:36:28 -0000 1.4 +++ dlls/ntdll/virtual.c 28 Apr 2003 00:05:58 Troy> -0000 @@ -102,7 +102,8 @@ # define page_mask 0xfff # define Troy> page_shift 12 # define page_size 0x1000 -# define What version did you specify in ~/.wine/config [windows] version? I guess you ran in non NT mode. And I guess your change will do havoc to programs needing NT mode (like Xilix ISE). Probably the limit has to be set in dependance of the version emulated. 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

Re: Mac OS X Support (patch with diff -u)
by Pierre d'Herbemont April 28, 2003

April 28, 2003

On Sunday, April 27, 2003, at 10:09 PM, Pierre d'Herbemont wrote: > Hi, > Here is a patch which mostly enables compilation on Mac OS X. The > support is not full as there is still some makefiles issues on which I > can't find a *clean* correction and a new issue I discovered in this > cvs version related to the libwine_port and the getopt function. > I am sorry but there is still a lot of brokent things in this patch, it is only partially working on Mac OS X. I'll provide an other which will be better so, don't loose time while looking at this one... Sorry. Pierre

1 0

Re: Wine, WIDE & Unix (was: Support for pkgconfig)
by Brian Vincent (C) April 28, 2003

April 28, 2003

> Wide doesn't change that. In fact, being based on Wine, it will implicitly > benefit from all the integration work we do on the Wine side. But at that > point, people will ask: what is the difference between Wide, and just Wine > running in Gnome? I think the problems you're going to run into immediately are: 1) Wine still isn't that far along to support something like this, bigger problems need to be solved first. Not the least of which is just good integration with the existing distributions (which will solve 90% of the problems you'll run into creating your own desktop.) 2) Finding people to do the work. Right now there seems to be a problem finding someone to work on the config tool, let alone a full blown desktop with multiple integrated apps. 3) Documentation.. it's never been one of the strong points of the project and a whole desktop environment needs a lot of it. 4) API.. Alexandre made an excellent point that promoting an API designed by MS puts the ball in their court. Pretty hard to compete on even terms with a company that has a lot of talented, motivated people and a war chest bigger than the GNP of a lot of nations. I think the proper thing to do is write it up an outline of it and put it on the "Fun Projects" page. Maybe someone will find the time to work on it. --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

1 0

Re: Mac OS X Support (patch with diff -u)
by Marcus Meissner April 28, 2003

April 28, 2003

On Sun, Apr 27, 2003 at 10:09:43PM +0200, Pierre d'Herbemont wrote: > Hi, > Here is a patch which mostly enables compilation on Mac OS X. The > support is not full as there is still some makefiles issues on which I > can't find a *clean* correction and a new issue I discovered in this > cvs version related to the libwine_port and the getopt function. > > Sorry for the -u option, I thought it was enabled by default :( The PPC assembly stuff appears correct to me :) Ciao, Marcus

2 1

New patch for WINE support in valgrind uploaded to sourceforge
by Adam Gundy April 28, 2003

April 28, 2003

A new version of the patch to valgrind needed to support WINE has been uploaded to Sourceforge: http://sourceforge.net/tracker/index.php?func=detail&aid=710006&group_id=46… It should apply cleanly to current valgrind CVS. This version of the patch will now work with an unmodified WINE CVS version. This is because it now _fully_ implements clone() support - ie it really does create system level threads. Currently only one thread can run at a time, so there are no locking issues in the main valgrind code. To use with WINE, you need to get a CVS checkout of valgrind, then apply the patch using: export CVSROOT=:pserver:anonymous(a)cvs.sourceforge.net:/cvsroot/valgrind cvs login cvs co valgrind patch -p0 < valgrind-wine.patch.13 then build and install valgrind: autogen.sh ./configure make install Get a CVS checkout of WINE by following the instructions at: http://www.winehq.com/?page=cvs then configure (for debugging) and build: CFLAGS=-g ./configure make depend && make install now you can start looking for bugs in WINE, and bugs in your own (debug) Windows code. Copy any DLLs/EXEs to somewhere WINE can get to them, plus copy any .PDB files that go with them into the same directory. Run WINE under valgrind using eg: valgrind --num-callers=30 --workaround-gcc296-bugs=yes wine notepad.exe or even: valgrind --num-callers=30 --workaround-gcc296-bugs=yes --gdb-attach=yes wine notepad.exe enjoy. Seeya, Adam -- Real Programmers don't comment their code. If it was hard to write, it should be hard to read, and even harder to modify. These are all my own opinions.

1 0

Crash in BeginPaint running Sams Photofact index, a free VB app
by Dan Kegel April 28, 2003

April 28, 2003

Wine is coming along! It can *almost* run a real world VB app I downloaded tonight. I'm trying to fix an old TV, and I wanted to see if Sams has a manual for it, so I downloaded their index program (http://www.servicesoftware.com/sams/) and was happy to discover it installed properly under a recent Wine (once I copied in the msiexec stuff, stdole2.tlb, etc.). However, it didn't quite run properly. Here's what I got running it under wine-20030408: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x409e5873). In 32-bit mode. 0x409e5873 (BeginPaint+0x9f [painting.c:200] in user32.dll.so): movl %eax,0x0(%edx) 203 if (!lps->hdc) Wine-dbg>bt Backtrace: =>0 0x409e5873 (BeginPaint+0x9f(hwnd=0x10029, lps=0x0) [painting.c:200] in user32.dll.so) (ebp=40892bc4) 1 0x52195475 (GRIDX.OCX..text+0x14475 in C:\WINDOWS\SYSTEM\GRIDX.OCX) (ebp=40892c18) 2 0x52194fe0 (GRIDX.OCX..text+0x13fe0 in C:\WINDOWS\SYSTEM\GRIDX.OCX) (ebp=40892c40) 3 0x5218b961 (GRIDX.OCX..text+0xa961 in C:\WINDOWS\SYSTEM\GRIDX.OCX) (ebp=40892c88) 4 0x409cc817 (WINPROC_wrapper+0x17 in user32.dll.so) (ebp=40892cac) 5 0x409cc875 (WINPROC_CallWndProc+0x55(proc=0x41855438, hwnd=0x10029, msg=0xf, wParam=0x0, lParam=0x0) [winproc.c:185] in user32.dll.so) (ebp=40892cd8) 6 0x409d1535 (CallWindowProcA+0xf9(func=0x40df0908, hwnd=0x10029, msg=0xf, wParam=0x0, lParam=0x0) [winproc.c:2812] in user32.dll.so) (ebp=40892d0c) 7 0x409b5a3e (DispatchMessageA+0x96(msg=0x40892d68) [message.c:794] in user32.dll.so) (ebp=40892d50) 8 0x66014979 (MSVBVM60.DLL.__vbaInStr+0x3b7 in C:\WINDOWS\SYSTEM\MSVBVM60.DLL) (ebp=40892d90) 9 0x660148b2 (MSVBVM60.DLL.__vbaInStr+0x2f0 in C:\WINDOWS\SYSTEM\MSVBVM60.DLL) (ebp=40892dd4) 10 0x66014790 (MSVBVM60.DLL.__vbaInStr+0x1ce in C:\WINDOWS\SYSTEM\MSVBVM60.DLL) (ebp=6601a360) 11 0x66010e00 (MSVBVM60.DLL.BASIC_CLASS_QueryInterface+0x17 in C:\WINDOWS\SYSTEM\MSVBVM60.DLL) (ebp=660d3526) 12 0x0c2474ff (SAMSINDX.exe..rsrc+0xbe334ff) (ebp=0424448b) *** Invalid address 0x0424448b (SAMSINDX.exe..rsrc+0x3e3048b) I can run this app under real Windows, but this is such a juicy little testcase I bet someone will want to take a look at it :-) - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

2 1

New plans for wintab work.
by Robert North April 27, 2003

April 27, 2003

Ok, Here are my plans for wintab work. If Aric's pach is considered ready to go into CVS, then I can start working on this in the following areas: Painter support. I beleive there are some problems getting Painter to work with wintab. This is my priority. Additional configuration for wintab. Aric's wintab reqires no configuration. It is only targeted at Intuos tablets. My implementation was to have a zero config default for the intuos2 tablet, similar to Aric's. Config could be provided where necessary to modify how an intuos tablet is seen by wintab, or to allow other tablet types to be used by wintab. I could merge this work into Aric's implementation. This would require significant re-factoring of Aric's data structs to match the more generic data structs I implemented. I may not have too much time to do work for the next 3 weeks, but I'd hope to make some progress on the painter side. Comments/questions welcome. -Rob.

2 1

X11DRV_DIB_CreateDIBSection
by Robert Lunnon April 27, 2003

April 27, 2003

Under Solaris I have a problem with this function.which appears to protect a section of the DIB giving a portion of it no access at all and when the application tries to blit from it later, a segfault results. Anyone had any similar experiences/know of this problem ? The offending application was little fighter II ntdll.dll.so`VIRTUAL_SetProt() ntdll.dll.so`VirtualProtectEx+0x27() ntdll.dll.so`VirtualProtect+0x23() x11drv.dll.so`X11DRV_DIB_DoProtectDIBSection+0x43() x11drv.dll.so`X11DRV_DIB_CreateDIBSection+0x32d() gdi32.dll.so`DIB_CreateDIBSection+0x4b() ddraw.dll.so`create_dib+0x14e() ddraw.dll.so`DIB_DirectDrawSurface_Construct+0xe3(dd5c2da0, dd5c16c8, dd532648) ddraw.dll.so`DIB_DirectDrawSurface_Create+0x6c() ddraw.dll.so`Main_create_offscreen+0x42() ddraw.dll.so`create_offscreen+0x105() ddraw.dll.so`Main_DirectDraw_CreateSurface+0xed() ddraw.dll.so`IDirectDrawImpl_CreateSurface+0x2f() 0x439a00()

2 1