- Wine-Devel - list.winehq.org

RH 7.1 gcc fixes compiler bug
by James Juran April 17, 2001

April 17, 2001

As discovered about two weeks ago by Francois Jacques and Ulrich Weigand, Red Hat's gcc-2.96-69 package has a bug which shows up in the HOOK_CallHook function in windows/hook.c (and possibly other places). Red Hat 7.1 contains gcc-2.96-81, which fixes this bug. Users of Red Hat 7.0 should install the gcc and cpp packages from Red Hat 7.1 to fix this problem. -- James Juran jamesjuran(a)alumni.psu.edu

1 0

Re: strange msvcrt crash
by gerard patel April 17, 2001

April 17, 2001

At 02:47 PM 16/04/2001 -0700, you wrote: > > Also I had lost of trouble running mspaint when using the builtin >msvcrt. None of the following works: >$ wine /mnt/win98/Program\ Files/Accessories/mspaint.exe >$ wine "/mnt/win98/Program Files/Accessories/mspaint.exe" >$ wine "c:/Program Files/Accessories/mspaint.exe" >$ wine "c:\\Program Files\\Accessories\\mspaint.exe" > > They all tell me that 'H:\wine\Files\Accessories\mspaint.exe was not >found.'. If I use native msvcrt they all work (and wine is the real >thing, not a script). Msvcrt includes command line parsing to give apps argc and argv - the current builtin handling in dlls/msvcrt/data.c is probably the cause of your problem : while (1) { if ((cmdline[end]==' ') || (cmdline[end]=='\0')) { if (cmdline[end]=='\0') last_arg=1; else cmdline[end]='\0'; Gerard

1 0

Re: strange msvcrt crash
by Alexandre Julliard April 16, 2001

April 16, 2001

Andreas Mohr <a.mohr(a)mailto.de> writes: > Err, which debugger ?? > > I get "Segmentation fault", and that's it... The automatic debugger startup cannot work in this case, because it only triggers for exception that are not handled by the application. But if you run the application under the debugger from the start, it should break at the first exception. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: strange msvcrt crash
by Alexandre Julliard April 16, 2001

April 16, 2001

Andreas Mohr <a.mohr(a)mailto.de> writes: > Call msvcrt.mktime(405b614c) ret=5f40e3b3 tid=08066638 > Ret msvcrt.mktime() retval=3adae6b2 ret=5f40e3b3 tid=08066638 > trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 > trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=c0000005 flags=0 > Call ntdll.RtlRaiseException(404a4aa8) ret=405e1056 tid=08066638 > trace:seh:EXC_RtlRaiseException code=80000100 flags=1 > trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 80000100 is EXCEPTION_WINE_STUB; the app probably called a stub from the exception handler of the first seg fault (and then called the same stub from the handler of the stub exception, etc.) The debugger should be able to tell you more about it. -- Alexandre Julliard julliard(a)winehq.com

3 2

Re: OpenGL Visual Management
by lawson_whitney＠juno.com April 16, 2001

April 16, 2001

On Mon, 26 Mar 2001, Gavriel State wrote: > This patch fixes several issues with the way OpenGL manages visuals: > > - It always uses a double-buffered visual if one is available, even when > not running Wine in --desktop mode. Previously, we just hoped that the > default visual was double buffered, which is isn't in some DRI GL drivers. > > - It ensures that all colormaps created use the double-buffered visual if > it exists. This prevents problems where DRI GL implementations fail > to work unless the colormap visual matches the window visual matches the > glX visual. > > - It gets around similar visual issue with the default GL context created for > apps that don't create their own contexts before trying to use GL functions. > > Note that we are not able to support the wgl ChoosePixelFormat/DescribePixelFormat > APIs properly. Some of the infrastructure for this exists in graphics/x11drv/opengl.c > so that it can be done when the time comes. This patch explicitly removes the wgl > code that tries to match the OpenGL visual to a requested pixel format, because > that won't work until we can dynamically remap HWNDs to new X11 Windows with > a new visual. > > -Gav > Something is not right, I think. Ordinary apps (Dmitry's About.exe, say) look as if they were using a vga16 server - unless the pointer is over the desktop: then the entire X display is black and white. Without a desktop with managed moving the pointer over the app's window radically changes the palette for the whole screen, but not to black and white. With neither managed nor desktop, the pointer has no effect on the palette. No doubt I am not well set up for DGA: grep -i dga config.cache ac_cv_header_X11_extensions_xf86dga_h=${ac_cv_header_X11_extensions_xf86dga_h=yes} ac_cv_lib_Xxf86dga_XDGAQueryExtension=${ac_cv_lib_Xxf86dga_XDGAQueryExtension=no} ac_cv_lib_Xxf86dga_XF86DGAQueryExtension=${ac_cv_lib_Xxf86dga_XF86DGAQueryExtension=yes} but I don't see why DGA support should disturb things so. I haven't really looked into it much yet...maybe you will see right off what you or I have done wrong? Regards, Lawson ---cut here ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/tagj.

2 11

strange msvcrt crash
by Andreas Mohr April 16, 2001

April 16, 2001

Hi all, (sorry for the long posting, but I think it's needed) wine --debugmsg +relay,+seh mspaint.exe, clicking on File->Send gives: Call kernel32.FindFirstFileA(403c71d0 "G:\\afxe6b2.tmp",405b61dc) ret=5f45b90c tid=08066638 Ret kernel32.FindFirstFileA() retval=403d26ca ret=5f45b90c tid=08066638 Call kernel32.FindClose(403d26ca) ret=5f45b91a tid=08066638 Ret kernel32.FindClose() retval=00000001 ret=5f45b91a tid=08066638 Call kernel32.FileTimeToLocalFileTime(405b61e0,405b61bc) ret=5f40e2ec tid=08066638 Ret kernel32.FileTimeToLocalFileTime() retval=00000001 ret=5f40e2ec tid=08066638 Call kernel32.FileTimeToSystemTime(405b61bc,405b61ac) ret=5f40e302 tid=08066638 Ret kernel32.FileTimeToSystemTime() retval=00000001 ret=5f40e302 tid=08066638 Call msvcrt.mktime(405b614c) ret=5f40e3b3 tid=08066638 Ret msvcrt.mktime() retval=3adae6b2 ret=5f40e3b3 tid=08066638 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=c0000005 flags=0 Call ntdll.RtlRaiseException(404a4aa8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a4788) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a4468) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a4148) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a3e28) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a3b08) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a37e8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a34c8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a31a8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a2e88) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a2b68) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a2848) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a2528) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a2208) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a1ee8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Call ntdll.RtlRaiseException(404a1bc8) ret=405e1056 tid=08066638 trace:seh:EXC_RtlRaiseException code=80000100 flags=1 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=1 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x4005ca10 code=80000100 flags=11 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x5f493fcb code=80000100 flags=11 Segmentation fault Any idea what's going on here ? Somehow the mktime() call seems to be a bit unhealthy. Not to mention the seh mess... Andreas Mohr

2 1

Re: Traces: fs -> tid
by Alexandre Julliard April 16, 2001

April 16, 2001

Francois Gouget <fgouget(a)free.fr> writes: > Also, this is why I think it's nice to have the tid on each trace. If > not using +relay there is no indication of which thread is issuing the > trace. I'm not opposed to a +tid option to switch on thread information on all traces. But I think +relay should always display the thread info, we will get too many useless traces if it doesn't. -- Alexandre Julliard julliard(a)winehq.com

4 5

InstallShield (resend)
by Daniel Walker April 15, 2001

April 15, 2001

I've been working on getting the Free Borland installer working. It uses installshield so I think this pertains to all installshield installers .. I've found a problem in propsheet.c , PROPSHEET_CollectPageInfo() . It appears that the property pages that come out of the installer have the PSP_USETITLE flag set. So wine attempts to get the title from the pszTitle field. The problem occurs because the pszTitle field is null. Wine try's to use it as a resource ID then fails. From reading over some MS docs I think windows, in this situation, reverts the PSP_USETITLE flag then uses the title in the template. So far I can get the installer to work, but it doesn't have a title or caption I haven't figured out why. I tryed changind it to "if (dwFlags & PSP_USETITLE && LOWORD(lppsp->pszTitle) != 0)" but it didn't have any effect. I also tryed reverting the PSP_USETITLE flag with no effect. Anyone have any ideas why there isn't a title? The patch below should fix the borland installer and , I assume, other install shield installers. Let me know if this patch doesn't work.. Daniel Walker --- ./dlls/comctl32/propsheet.c Mon Feb 12 10:08:31 2001 +++ ../../wine-20010305/dlls/comctl32/propsheet2.c Sat Apr 14 17:22:59 2001 @@ -296,12 +296,10 @@ if (dwFlags & PSP_USETITLE) { - if ( !HIWORD( lppsp->pszTitle ) ) - { char szTitle[256]; - - if ( !LoadStringA( lppsp->hInstance, (UINT) lppsp->pszTitle, szTitle, 256 ) ) - return FALSE; + + if ( !HIWORD( lppsp->pszTitle ) && LoadStringA( lppsp->hInstance, (UINT) lppsp->pszTitle, szTitle, 256 ) ) + { psInfo->proppage[index].pszText = HEAP_strdupAtoW(GetProcessHeap(), 0, szTitle );

1 0

Strange crash
by Dmitry Timoshkov April 15, 2001

April 15, 2001

Hello all. Could anybody help to find the source of the following crash? Do this crash look known to somebody? ... Unhandled exception: c000008f in 32-bit code (0x40897fde). In 32-bit mode. Symbol h_errno is invalid Symbol hack_digit is invalid 0x40897fde (X11DRV_PEN_SelectObject+0x8e [pen.c:69]): fldcw 0xfffffffe(%edx) 69 } Wine-dbg>bt Backtrace: =>0 0x40897fde (X11DRV_PEN_SelectObject+0x8e(dc=0x4038bbbc, hpen=0xffe7, pen=0x40842034) [pen.c:69]) (ebp=41f35aac) 1 0x40895a73 (X11DRV_SelectObject+0xb3(dc=0x4038bbbc, handle=0xffe7) [objects.c:62]) (ebp=41f35ad0) 2 0x4082a789 (SelectObject+0x75(hdc=0x68, handle=0xffe7) [gdiobj.c:867]) (ebp=41f35af0) 3 0x4081fceb (DC_InitDC+0x47(dc=0x4038bbbc) [dc.c:163]) (ebp=41f35b08) 4 0x40820919 (CreateDCA+0x135(driver=0x4083745d, device=0x0, output=0x0, initData=0x0, s=0x0, s=0x0, s=0x4083745d) [dc.c:579]) (ebp=41f35c50) 5 0x40823ddc (CreateDIBitmap+0x144(hdc=0x60, header=0x4038b4ec, init=0x4, bits=0x407bc308, data=0x4038b4ec, coloruse=0x0) [dib.c:850]) (ebp=41f35c80) 6 0x40782069 (CURSORICON_CreateFromResource+0x2dd(hInstance=0x0, hObj=0x0, bits=0x407bc2a0, cbSize=0x2e8, bIcon=0x1, dwVersion=0x30000, width=0x20, height=0x20, loadflags=0x8040) [cursoricon.c:550]) (ebp=41f35d14) 7 0x40782647 (CURSORICON_Load+0x257(hInstance=0x106, name=0x7f00, width=0x20, height=0x20, colors=0x100, fCursor=0x0, loadflags=0x8040) [cursoricon.c:777]) (ebp=41f35d64) 8 0x40784da7 (LoadImageW+0x12f(hinst=0x0, name=0x7f00, type=0x1, desiredx=0x20, desiredy=0x0, loadflags=0x8040) [cursoricon.c:2268]) (ebp=41f35d98) 9 0x40784c4e (LoadImageA+0x7e(hinst=0x0, name=0x7f00, type=0x1, desiredx=0x0, desiredy=0x0, loadflags=0x8040) [cursoricon.c:2208]) (ebp=41f35dcc) 10 0x407840c6 (LoadIconA+0x26(hInstance=0x0, name=0x7f00) [cursoricon.c:1792]) (ebp=41f35df0) ... Commenting lines 36-37 physDev->pen.width = GDI_ROUND((FLOAT)pen->logpen.lopnWidth.x * dc->xformWorld2Vport.eM11 * 0.5); in X11DRV_PEN_SelectObject (graphics/x11drv/pen.c) cures the problem. Why call to floor() leads to crash?

1 0

KC Wine & WWN
by Brian Vincent (C) April 15, 2001

April 15, 2001

Over the last few days I've talked with Eric Pouech and Zack Brown about taking over the KC Wine and Wine Weekly News updates. It looks like I've got the first issue ready to go. Anyway, here's just some of my thoughts on it, and I'd welcome any and all feedback: - Right now my ISP at home is really messed up. At least in the short term I'll be doing a lot of this at work. Unfortunately that means I'll be mostly using Hypermail archives and some really editing methods. I won't be subscribed to the list, but I'll gladly receive email at the address below. - Unfortunately that also means I don't have CVS access right now. At some point I'd like to get WWN going again, but it might be several weeks. - Also, I always like the CVS commit summary, who used to write that? I'd like to incorporate that into the KC Wine page eventually. - My technical skills are not nearly as good as Eric's. So some of my summaries might be a little off. Hopefully I'll get better over time. - IMHO, these updates are a great PR tool for the project. Screenshots, product reviews, and news stories about Wine are very helpful. I'd encourage all of you to send me any news like this. I'll definitely include it. - Along those same lines, in the future I'll probably setup a screenshots page or something like that. ------------ Brian Vincent Copper Mountain Telecom brianv(a)ski-copper.com

2 1