- wine-devel - winehq.org

Notes2Paper with wine
by ralf schwarzmaier 21 Apr '01

21 Apr '01

hi @ll i have an problem with notes2paper under wine .... i need this for some databases of Notes. my lotus notes client runs perfect, but the additional programm notes2paper not, i can install notes2paper without any problems, direct in wine, but when i start it, it crash with non error message. what can i do, or what are teh parameters for an development debuging log ? thank you bye ralf

1 0

GDB remote debugging for wine
by Ove Kaaven 21 Apr '01

21 Apr '01

As we all know, gdb isn't very compatible with wine, since gdb makes so many assumptions about the operating environment that isn't true in wine. But lately it occurred to me that perhaps it's possible to use gdb's remote debugging features to solve these issues. So recently, I've been secretly experimenting with writing gdb-server code in the wineserver. It goes something like this... ./configure --enable-remote-gdb [...blah...] $ wine stuff gdb socket ready at: target remote localhost:1234 $ gdb wine (gdb) target remote localhost:1234 and you're currently able to look at registers, backtrace, list all the threads, change thread, and read process memory... neato. But its usefulness might be quite limited since gdb doesn't know about the dynamically-loaded dlls so it doesn't automatically load their symbols... does anyone have ideas on how to solve that? It doesn't appear that the standard remote protocol have a command to tell gdb, and I don't know how gdb ordinarily does it. I've pondered making wine generate a file full of "add-symbol-file" commands or something that could be executed by gdb, but I don't know how to do that cleanly... preferably hacks for loading symbols should be transparent to the developer, and new symbols loaded automatically after new dlls are loaded. Hmm...

2 1

Crash due to some fixme messages in CreateProcessA
by Lionel Ulmer 20 Apr '01

20 Apr '01

Hi all, While running a program, I got a crash in the CreateProcessA, in the following debug TRACE line : if (lpStartupInfo->lpDesktop) FIXME("(%s,...): lpStartupInfo->lpDesktop %s ignored\n", name, lpStartupInfo->lpDesktop); By running the debugger, I got this : Wine-dbg>print *lpStartupInfo print *lpStartupInfo {cb=83886080, lpReserved=*** Invalid address 0x4c000000 (_end+0xb823758) , lpDesktop=*** Invalid address 0x4c403416 (_end+0xbc26b6e) , lpTitle=*** Invalid address 0x70403416 (_end+0x2fc26b6e) , dwX=1883255830, dwY=406860822, dwXSize=1107296256, dwYSize=-1795162040, dwXCountChars=1849690049, dwYCountChars=1819042932, dwFillAttribute=1819042862, dwFlags=791899392, wShowWindow=26988, cbReserved2=14946, lpReserved2=*** Invalid address 0x7273752f (_end+0x31f5ac87) , hStdInput=409955375, hStdOutput=1107296256, hStdError=-285212600} It means that we are seeing a very broken application where these fields (lpDesktop and lpTitle) do not seem to be filled in propery... Now I never tried running this application on Windows to test if it even works, but I suppose it should work (otherwise it would not be burned on the CD :-) ). So what should we do ? Suppress the '%s' and replace it with a '%p' ? Add a check on the pointer to see if it's valid ? Lionel PS: BTW, why is this application that is on a win95 filesystem get run as : Call kernel32.CreateFileA(00405070 "~inst.exe",40000000,00000000,00000000,00000002,00000080,00000000) ret=00401391 tid=080678a0 Thus leading to a "~inst.exe" not found... -- Lionel Ulmer - http://www.bbrox.org/

2 2

FONT 8 requested, but 6x12 choosen: Wrong setup?
by Uwe Bonnes 20 Apr '01

20 Apr '01

Hallo, the entry dialog of the Encarta 99 setup (from Computer Bild) looks wrong on my system: The box is to small and graphics and text overlap. This is caused by CreateDialogIndirect requesting an Font with width 8, but wine choosing a font with width 6. Manually correcting the return value of DIALOG_GetCharSizeFromDC to 8 gets the visula impression right. Is this caused by me setting up something wrong? Any hints how to setup right? Call USER.219: CREATEDIALOGINDIRECT(0x02fe,058f:0008,0x0390,0x02ef7778) ret=02ef:76b5 ds=02ff trace:dialog:DIALOG_ParseTemplate16 DIALOG 0, 0, 293, 214 trace:dialog:DIALOG_ParseTemplate16 STYLE 50000040 trace:dialog:DIALOG_ParseTemplate16 CAPTION '' trace:dialog:DIALOG_ParseTemplate16 FONT 8,'Helv' trace:font:X11DRV_FONT_SelectObject hfont=ffed trace:font:XFONT_RealizeFont physfont 1 trace:font:CreateFontIndirectW (-10 0 0 0) 'L"Helv"' => 09f6 trace:font:XFONT_UnAlias found alias 'Helv'->Helvetica' trace:font:X11DRV_FONT_SelectObject hfont=09f6 trace:font:XFONT_MatchDeviceFont (1) 'Helvetica' h=-10 weight=0 trace:font:XFONT_MatchDeviceFont found facename 'Helvetica' trace:font:XFONT_Match [ 10pt h=12 w=6 Bold Italic] trace:font:XFONT_Match returning 518 ... trace:font:XFONT_Match [ 12pt h=18 w=10 Normal ] trace:font:XFONT_Match returning 560 trace:font:XFONT_Match [ 13pt h=20 w=11 Normal ] trace:font:XFONT_Match returning 576 trace:font:XFONT_Match [ 17pt h=27 w=14 Normal ] trace:font:XFONT_Match returning 624 trace:font:XFONT_Match [ 23pt h=35 w=19 Normal ] trace:font:XFONT_Match returning 688 trace:font:LFD_ComposeLFD LFD(uRelax=0): -adobe-helvetica-medium-r-normal-*-11-*-100-100-p-*-iso8859-1 trace:font:XFONT_RealizeFont physfont 3 trace:font:GetTextMetricsW text metrics: Weight = 400 FirstChar = 32 AveCharWidth = 6 Italic = 0 LastChar = 255 MaxCharWidth = 11 UnderLined = 0 DefaultChar = 32 Overhang = 0 StruckOut = 0 BreakChar = 32 CharSet = 0 PitchAndFamily = 21 -------------------- InternalLeading = 2 Ascent = 10 Descent = 2 Height = 12 trace:font:GetTextExtentPointA not bug compatible. trace:font:GetTextExtentPoint32A (00000088 "abcd"... 4 0x407c6c8c): returning 22 x 12 trace:dialog:DIALOG_GetCharSizeFromDC Using tm: 6x12 (dlg: 6 x 12) (variable) Bye Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Free Software: If you contribute nothing, expect nothing --

1 0

Re: Strange crash
by gerard patel 20 Apr '01

20 Apr '01

At 10:30 AM 20/04/2001 +0200, you wrote: <snip> >The lower 6 bits are the new floating point exception masks. Mine are >all set and yours are cleared, therefore the crash. > >Why that is the case, I haven't got a clue. I'm not sure I followed everything, but it could come from a problem that occurred a lot of time before, no? The bits could be already cleared on entry of the subroutine. If the exception handling bits are cleared and the app don't do anything with floating point, nothing will break, AFAICT. If this is the case a way could be to patch the code to print the mask with every +relay operation. BTW, I wonder if Dmitry has done some classic tricks like - getting a fresh tree from Winehq - compiling everything with -O0 - trying the same app on another computer with a (as much as possible) different configuration. Gerard

2 1

problem with native dll's.
by Rein Klazes 20 Apr '01

20 Apr '01

Hi, Since the cvs commits early this week or the last (I could be more precise but that will take a while) I have noticed a problem with some native dlls. If I start one app that uses such a dll and then another using the same dll may crash. If this second app is started as the first process it runs fine. As an example eudora, using native commctrl/comctl32 crashes when it loads these dlls: | Unhandled exception: priviledged instruction | in 32-bit code (0x406e12b8). | In 32-bit mode. | 0x406e12b8 (GetTextColor+0x34 [dcvalues.c:177]): hlt | 177 DC_GET_VAL( COLORREF, GetTextColor, textColor ) | Wine-dbg>bt | Backtrace: | =>0 0x406e12b8 (GetTextColor+0x34(hdc=0x0) [dcvalues.c:177]) (ebp=405b6dc4) | 1 0xbfebbd8d (COMCTL32.DLL.341+0x74) (ebp=405b6dd8) | 2 0xbfebbceb (COMCTL32.DLL.EntryPoint+0x36) (ebp=405b6e04) | 3 0x4008abe3 (MODULE_InitDLL+0x97(wm=0x40383d84, type=0x1, lpReserved=0x1) [module.c:115]) (ebp=405b6e24) | 4 0x4008acf1 (MODULE_DllProcessAttach+0xd1(wm=0x40383d84, lpReserved=0x1) [module.c:182]) (ebp=405b6e48) | 5 0x4008accd (MODULE_DllProcessAttach+0xad(wm=0x403838f4, lpReserved=0x1) [module.c:177]) (ebp=405b6e68) | 6 0x4008accd (MODULE_DllProcessAttach+0xad(wm=0x4038302c, lpReserved=0x1) [module.c:177]) (ebp=405b6e88) | 7 0x4008accd (MODULE_DllProcessAttach+0xad(wm=0x403826f8, lpReserved=0x1) [module.c:177]) (ebp=405b6ea8) | 8 0x4008accd (MODULE_DllProcessAttach+0xad(wm=0x0, lpReserved=0x1) [module.c:177]) (ebp=405b6ec8) | 9 0x400d288f (start_process+0x133 [process.c:373]) (ebp=405b6f30) | 10 0x400d5f99 (SYSDEPS_DoCallOnStack+0x25(func=0x400d275c, arg=0x0) [sysdeps.c:173]) (ebp=405b6ff0) | 11 0x400d603f (SYSDEPS_CallOnStack+0x2f) (ebp=bffff8d4) | 12 0x400d60e2 (SYSDEPS_SwitchToThreadStack+0x8e(func=0x400d275c) [sysdeps.c:236]) (ebp=bffff908) | 13 0x400d2c5d (PROCESS_InitWine+0x1a1(argc=0x5, argv=0xbffff9a4, win16_exe_name=0x804d5c0, win16_exe_file=0x804d6c4) [process.c:524]) (ebp=bffff924) | 14 0x0804c164 (Letext [main.c]) (ebp=bffff93c) | 15 0x4028116b (NTDLL.DLL.sqrt+0x3bc6b) (ebp=bffff978) | 16 0x08049021 (_start+0x21) (ebp=00000000) The ip register is pointing to some instruction byte, making it an bogus opcode, "hlt" in this case: | Wine-dbg>disass $eip-12,$eip+10 | 0x406e129c (GetTextColor+0x18 [dcvalues.c:177]): call 0x406bf664 (_init+0x67c) | 0x406e12a1 (GetTextColor+0x1d [dcvalues.c:177]): addl $4,%esp | 0x406e12a4 (GetTextColor+0x20 [dcvalues.c:177]): testl %eax,%eax | 0x406e12a6 (GetTextColor+0x22 [dcvalues.c:177]): jz 0x406e12b4 (GetTextColor+0x30 [dcvalues.c:177]) | 0x406e12a8 (GetTextColor+0x24 [dcvalues.c:177]): movl 0x88(%eax),%edi | 0x406e12ae (GetTextColor+0x2a [dcvalues.c:177]): pushl %esi | 0x406e12af (GetTextColor+0x2b [dcvalues.c:177]): call 0x406bfee4 (_init+0xefc) | 0x406e12b4 (GetTextColor+0x30 [dcvalues.c:177]): movl %edi,%eax | 0x406e12b6 (GetTextColor+0x32 [dcvalues.c:177]): leal 0xfffffff4(%ebp),%esp | 0x406e12b9 (GetTextColor+0x35 [dcvalues.c:177]): popl %ebx | 0x406e12ba (GetTextColor+0x36 [dcvalues.c:177]): popl %esi | 0x406e12bb (GetTextColor+0x37 [dcvalues.c:177]): popl %edi | 0x406e12bc (GetTextColor+0x38 [dcvalues.c:177]): leave | 0x406e12bd (GetTextColor+0x39 [dcvalues.c:177]): ret $0x4 | 0x406e12c0 (GetViewportExt16 [dcvalues.c:182]): pushl %ebp Redoing the experiment (by starting and stopping all apps's) will give crashes at slightly different places. Has any one a suggestion? Rein. -- Rein Klazes rklazes(a)xs4all.nl

1 0

Re: Strange crash
by Alexandre Julliard 20 Apr '01

20 Apr '01

"Dmitry Timoshkov" <dmitry(a)sloboda.ru> writes: > Unhandled exception: c000008f > [...] > > 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? Exception c000008f is EXCEPTION_FLT_INEXACT_RESULT. Probably one of the floating point values is invalid, or something similar. -- Alexandre Julliard julliard(a)winehq.com

4 10

Regedit from Win2k
by Dominik Strasser 19 Apr '01

19 Apr '01

Hi, trying to run regedit from Win2k I encounter the following problems: err:win32:fixup_imports No implementation for shlwapi.dll.0(StrRetToBufA) imported from shell32.dll, setting to 0xdeadbeef err:win32:fixup_imports No implementation for shlwapi.dll.0(StrRetToBufW) imported from shell32.dll, setting to 0xdeadbeef Hmm, but those are implemented. When I try to add a loadorder for shlwapi to get the builtin one, this doesn't work. "shlwapi" = "builtin, native" Still the native version is used. If I change the overall DefaultLoadOrder, to "builtin, native" it works. After this, the tree items in the Treeview vanished but I don't care. I assume this is the cause: fixme:listview:LISTVIEW_Create ANSI notify format is NOT used Trying to save the registry I get a crash wich I tracked down to this line in filedlg95.c: 453: AllocInArgWtoA(ofn->lpTemplateName, lpTemplateName); But ofn->lpTemplateName is not a pointer but seems to be a handle: 0x00000064. If I wrap the call into a if(!IsBadReadPtr(ofn->lpTemplateName, 4)), the filedialog comes up. Any clues anybody ? Regards Dominik -- Dominik Strasser | Phone: +49 89 636-43691 SIEMENS AG | Fax: +49 89 636-42284 CT SE 4 | E-Mail:Dominik.Strasser@mchp.siemens.de Otto-Hahn-Ring 6 | D-81739 Muenchen | Room: 53-263

1 0

Re: Store each glyph name only once in PS driver
by Alexandre Julliard 18 Apr '01

18 Apr '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > Separating the string data from their indices will allow them to be > declared as const, so that should get them into the ".rodata" section of > the resulting assembly; the Adobe Glyph List vector is already there. > Is this what you mean by "read only memory"? Yes, exactly that; separating the strings and the indices seems the right thing to do. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Store each glyph name only once in PS driver
by Alexandre Julliard 18 Apr '01

18 Apr '01

Ian Pilcher <ian.pilcher(a)home.com> writes: > typedef struct { > + INT index; > + CHAR sz[0]; > +} GLYPHNAME; > + > +typedef struct { > + LONG UV; > + GLYPHNAME *name; > +} UNICODEGLYPH; > + > +typedef struct { > + INT size; > + UNICODEGLYPH glyphs[0]; > +} UNICODEVECTOR; Zero-size arrays are not portable, and the standard method of using a size of 1 doesn't work well with initialized data (lots of warnings). So you probably need to change your data structures a bit; also it would be nice to store all the preinitialized stuff, or at least the strings, in read-only memory to save a bit of swap space. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: SEH logging
by Alexandre Julliard 17 Apr '01

17 Apr '01

Francois Gouget <fgouget(a)free.fr> writes: > In this implementation exception.c reuses format_exception_msg() > which is normally used to display the dialog box asking whether to debug > the exception or not. Since this is all in ntdll it works. Actually win32/except.c is part of kernel, it's only linked in ntdll now because separation is not finished. So you cannot call format_exception_msg from ntdll. And anyway this would print "unhandled xxx" for all exceptions, which is misleading since they might be handled later on. Also I don't think the core exception routines should know about specific exception codes like EXCEPTION_WINE_STUB. If you want a message on stubs, it should be done in the .spec.c file before the call to RtlRaiseException. -- Alexandre Julliard julliard(a)winehq.com

2 1

IStorage file format.
by Psyon 17 Apr '01

17 Apr '01

I am interested in making an HTMLHelp (.CHM) viewer for Linux. I am told the files are actually IStorage files. I have been scouring the internet looking for information about this format with no avail. I have also been looking over the WINE implementation, to see if that would shed some light on the format, but the code dives into a bunch of cryptic functions that I cant seem to follow. Is there any documents describing the format of these files? even just a brief description would be nice at this moment. If you have any information please replay directly to me at x-odus(a)iname.com Thanks in advance --Don Becker

4 3

RH 7.1 gcc fixes compiler bug
by James Juran 17 Apr '01

17 Apr '01

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 17 Apr '01

17 Apr '01

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 16 Apr '01

16 Apr '01

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 16 Apr '01

16 Apr '01

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 16 Apr '01

16 Apr '01

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 16 Apr '01

16 Apr '01

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 16 Apr '01

16 Apr '01

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 15 Apr '01

15 Apr '01

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 15 Apr '01

15 Apr '01

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) 15 Apr '01

15 Apr '01

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

InstallShield
by Daniel Walker 15 Apr '01

15 Apr '01

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

Re: debugger startup
by Alexandre Julliard 13 Apr '01

13 Apr '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > apart, from always using argv[0] (and transposing it to a windows > filename when needed), is there another fix ? You can set WINEPRELOAD to make sure we load the right file; so the exec would be something like: WINEPRELOAD=winedbg.so exec wine $* -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: debugger startup
by Alexandre Julliard 13 Apr '01

13 Apr '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > well, this has a major holes: > - since the process creation in Wine knows the created process is not > a PE image, it doesn't set the info on the server side for the newly > created process ; after the exec in the shell script, the info cannot > be retrieved from the parent, hence an error What makes you think that? Of course the info is set for non-PE binaries too, otherwise you could never debug a Winelib app. > perhaps, the best fix would be to merge the init_process/new_process > server calls I don't see how you could possibly do that. new_process is done by the parent, and init_process by the child; they serve very different purposes. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Strange behaviour with GETVDMPOINTER32W
by Alexandre Julliard 12 Apr '01

12 Apr '01

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > Hopefully I get the cutting and pasting right now... > > ... > Call KERNEL.88: LSTRCPY(0x045f781a,0x02ef7044 "%CMDLINE%") ret=02e7:0687 ds=02f7 > Ret KERNEL.88: LSTRCPY() retval=0x045f781a ret=02e7:0687 ds=02f7 > ... > Call KERNEL.516: GETVDMPOINTER32W(0x045f781a,0x0001) ret=02e7:ae4a ds=02f7 > Ret KERNEL.516: GETVDMPOINTER32W() retval=0x404951ba ret=02e7:ae4a ds=02f7 > ... > Call kernel32.lstrcmpA(404951ba "\021\021\021\021\021\021\021\021\021\021\021\021\021\021\0..."...,407e6cbc "%FINDWINDOWCL%") ret=10001464 tid=081df290 Well, either GetVDMPointer returns the wrong pointer, or someone has written to the buffer in the meantime. You need to show us the full trace if you want us to be able to help. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Strange behaviour with GETVDMPOINTER32W
by Alexandre Julliard 12 Apr '01

12 Apr '01

Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: > I don't understand this sequence: > > Some strings gets copied to segemented memory > Call KERNEL.88: LSTRCPY(0x046f0018,0x00ef0080 "") ret=02ef:069a ds=02ff > Ret KERNEL.88: LSTRCPY() retval=0x0467781a ret=02ef:0687 ds=02ff lstrcpy is supposed to return its first argument (0x046f0018 in this case). Something is very wrong here... -- Alexandre Julliard julliard(a)winehq.com

2 2

Re: edit control patch
by lawson_whitney＠juno.com 12 Apr '01

12 Apr '01

On Wed, 11 Apr 2001, Dan Engel wrote: > This is my first attempt at submitting a patch--please someone let me know if there are "customs" I need to follow. > Not meaning to beat on you, but - if somebody else patches the same file while you are working on it, it makes garbage of your diff. For a project as big and open as Wine, it is only common sense and common courtesy that we use diff -u. As well as + and - to show what changed, that has also context lines so patch can have some idea if it is FI adding lines where they belong. Besides, Alexandre prefers it. (From <wine>/README, which I think we should all read now and again :-) " If you add something, or fix a bug, please send a patch ('diff -u' format preferred) to julliard(a)winehq.com or to the wine-patches(a)winehq.com mailing list for inclusion in the next release. -- Alexandre Julliard julliard(a)winehq.com " Lawson This message is brought to you by Wine-20010326, junopine-2.0.2, Juno 2.0.11, and pine-4.10 ---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.

1 0

Re: edit control patch
by James Hatheway 12 Apr '01

12 Apr '01

Just one little comment, you should make your diffs using the -u (unified diff) option. (ie. cvs -d $CVSROOT -u controls/edit.c > newdiff.diff) That way your patch has "+"s and "-"s instead of ">"s. It makes it easier to read what is changing in the patch... (For example, you patch will look something like this instead:) + INT BkMode; + BkMode = GetBkMode(dc); + SetBkMode( dc, OPAQUE); + SetBkMode( dc, BkMode); -James -- James Hatheway Work: james(a)macadamian.com ~ http://www.macadamian.com Home: jhatheway(a)home.com ~ http://members.home.net/jhatheway "Man könnte froh sein, wenn die Luft so rein wäre wie das Bier" "One could be happy if the air were as pure as the beer" ----- Original Message ----- From: "Dan Engel" <dengel(a)sourceharvest.com> To: <wine-patches(a)winehq.com> Sent: Wednesday, April 11, 2001 10:24 PM Subject: edit control patch > This is my first attempt at submitting a patch--please someone let me know if there are "customs" I need to follow. > > Problem: Edit boxes are, in some cases, displaying selected text as white-on-white, so that it disappeared. > > Analysis: When text is drawn using the x11drv function X11DRV_ExtTextOut, the function does not paint a background rectangle if the background mode for the device context is transparent. In the case of edit controls, there is no attempt to change the background mode to opaque for selected text. > > Solution: In the case of painting reverse text in the edit control (function EDIT_PaintText) set the backgound mode to opaque, and then restore it before exiting the function. > > The patch is attached (wine.diff). > >

1 0

Strange behaviour with GETVDMPOINTER32W
by Uwe Bonnes 11 Apr '01

11 Apr '01

Hallo, I don't understand this sequence: Some strings gets copied to segemented memory Call KERNEL.88: LSTRCPY(0x046f0018,0x00ef0080 "") ret=02ef:069a ds=02ff Ret KERNEL.88: LSTRCPY() retval=0x0467781a ret=02ef:0687 ds=02ff ... This segmented memory gets mapped to linear memory Call KERNEL.516: GETVDMPOINTER32W(0x0467781a,0x0001) ret=02ef:ae4a ds=02ff Ret KERNEL.516: GETVDMPOINTER32W() retval=0x4043bda2 ret=02ef:ae4a ds=02ff ... Accessing the linear memory returns garbage Call kernel32.lstrcmpA(4043bda2 "\021\021\021\021\021\021... ... ret=10001464 tid=08404b48 I don't see any other accesses to 0x046f:0x0018 or 0x0467781a in between. This happens withthe Encarta 99 setup. Bye Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Free Software: If you contribute nothing, expect nothing --

1 0

Re: debugger startup
by Alexandre Julliard 11 Apr '01

11 Apr '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > either we decide that shell scripts shouldn't be used (easy > solution) or we could do something like : > - if the CreateProcess fails, then wait for a certain amount of > time. If after that time the current process isn't currently > debugged, then report the error. Otherwise assume what did happen is > what has been described above CreateProcess already waits a couple of seconds for the new process to show up, so it's probably enough to simply check for the debugger once CreateProcess returns. An easier fix may be to have the script exec the debugger instead of launching it as a child process; this way the debugger parent pid will be the original Wine process, and everything should work fine. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: VxD information
by Alexandre Julliard 11 Apr '01

11 Apr '01

Maurice van der Pot <griffon26(a)kfk4ever.com> writes: > I'd like to get started on VxD support, but I'm unable to find any useful > documentation on how it's implemented in Wine. I've been looking through > the sources (e.g. vxd.c, wprocs.spec) but I can't find the connection > between a call to int 2F and a call to the functions in vxd.c. The connection is through int 2f ax=0x1684 (in msdos/int2f.c), which does a GetProcAddress on wprocs and returns the vxd entry point to the application. The app then calls the corresponding vxd directly with a normal function call. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: RegSetValueEx problem?
by Alexandre Julliard 11 Apr '01

11 Apr '01

davep <davep(a)cyw.uklinux.net> writes: > I have now been able to build and run WineMine under NT4, and it works > perfectly. On exit each parameter is saved to the registry as 16 bytes including > the training garbage (not visible in Regedit of course) and when restarted the > exact same 16 bytes are reloaded from the registry. > > It does therefore seem that there is something wrong with Wne's implementation. No, it depends if data[sizeof(data)] is null or not; the +1 on the size is done only if the last byte is null, on the assumption that the programmer forgot to count it (i.e. used strlen(data) instead of strlen(data)+1). It's the usual Microsoft approach of hiding bugs instead of fixing them, and it is definitely what NT does (or we wouldn't be doing such a monstrosity). Now what can happen is that the Microsoft compiler lays out the stack in a different way than gcc, and that the variable that is just above the array on the stack doesn't contain 0 in this case. In fact I suspect that if you run your Windows binary of WineMine under Wine it will work fine too. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: Traces: fs -> tid
by Alexandre Julliard 11 Apr '01

11 Apr '01

Francois Gouget <fgouget(a)free.fr> writes: > Yes, but it would also be the simplest implementation (overdesign can > be ugly too). And if it's the one off hack that it current looks like it > is, why not. > I propose to just let Alexandre decide which implementation, if any, > he thinks would be worth including in CVS. I think we have now wasted enough bandwidth on this non-issue. The relay traces have always displayed the thread info, and will continue to do so. People who are morally offended by the extra 5 characters needed for the tid can hack their local tree, or learn to use sed/awk/perl. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: edit control patch
by Ian Pilcher 11 Apr '01

11 Apr '01

Dan Engel wrote: > > This is my first attempt at submitting a patch--please someone let me know if there are "customs" I need to follow. > Word-wrap is nice. :-) -- ======================================================================== Ian Pilcher ian.pilcher(a)home.com ========================================================================

1 0

Re: RegSetValueEx problem?
by Alexandre Julliard 11 Apr '01

11 Apr '01

gerard patel <gerard.patel(a)asi.fr> writes: > I have browsed server/registry.c and it seems that the registry > stores a terminating null for strings; so if you have in the registry > file a string like "0123456789", it get in memory a length of 11. > So I guess that the fix would be to fix the length by -1 somewhere > in the path server->ntdll->advapi No, the current behavior is correct for NT; what you want is a version check to get the Win95 behavior. Something like the patch below should do it (and of course WineMine should be fixed to work on NT too). Index: dlls/advapi32/registry.c =================================================================== RCS file: /opt/cvs-commit/wine/dlls/advapi32/registry.c,v retrieving revision 1.24 diff -u -r1.24 registry.c --- dlls/advapi32/registry.c 2001/03/23 19:12:01 1.24 +++ dlls/advapi32/registry.c 2001/04/09 20:49:35 @@ -640,8 +640,12 @@ { UNICODE_STRING nameW; - if (count && is_string(type)) + if (GetVersion() & 0x80000000) /* win95 */ { + if (type == REG_SZ) count = strlenW( (WCHAR *)data ) + sizeof(WCHAR); + } + else if (count && is_string(type)) + { LPCWSTR str = (LPCWSTR)data; /* if user forgot to count terminating null, add it (yes NT does this) */ if (str[count / sizeof(WCHAR) - 1] && !str[count / sizeof(WCHAR)]) @@ -663,7 +667,11 @@ WCHAR *dataW = NULL; NTSTATUS status; - if (count && is_string(type)) + if (GetVersion() & 0x80000000) /* win95 */ + { + if (type == REG_SZ) count = strlen(data) + 1; + } + else if (count && is_string(type)) { /* if user forgot to count terminating null, add it (yes NT does this) */ if (data[count-1] && !data[count]) count++; -- Alexandre Julliard julliard(a)winehq.com

2 1

VxD information
by Maurice van der Pot 11 Apr '01

11 Apr '01

I'd like to get started on VxD support, but I'm unable to find any useful documentation on how it's implemented in Wine. I've been looking through the sources (e.g. vxd.c, wprocs.spec) but I can't find the connection between a call to int 2F and a call to the functions in vxd.c. Regards, Maurice van der Pot.

1 0

Re: Traces: fs -> tid
by Alexandre Julliard 10 Apr '01

10 Apr '01

Francois Gouget <fgouget(a)free.fr> writes: > But maybe we could ask for traces generated with +relay,+tid instead > of just +relay. > Also when you're working on a specific application for which you have > determined that threads don't play a role, then you would have the > option of omitting the +tid to get simpler traces. I disagree, I think the thread information is important even if you are not chasing a thread problem, simply to tell you which calls are part of the same sequence. It's not possible to make sense of any relay trace if the calls made from different threads cannot be distinguished. If the tid really disturbs you, you can always pipe the output into a sed 's/tid=.*//' or something similar. -- Alexandre Julliard julliard(a)winehq.com

3 2

Traces: fs -> tid
by Francois Gouget 10 Apr '01

10 Apr '01

I noticed that fs was replaced by tid in relay (and snoop & co too now). I propose a slightly different version based on the following premises: * when suspecting a threading problem it could be nice to tag each trace with the id of the thread that emits it * when there's no thread issue, then fs and tid are unnecessary and only clutter the traces by making lines longer and harder to read * I find that lines are more readable if the thread id comes first as it's always the same length and doesn't mess up the alignment of the other fields So this patch adds a debug channel called 'tid' which activates printing the tid as the first field of all traces. Actually, it might make sense to merge 'tid' with the 'thread' debug channel. 'Screenshot': 08063178:Call user32.DispatchMessageA(405b6e50) ret=00402135 08063178:trace:relay:WINPROC_CallWndProc (wndproc=0x401c74,hwnd=00000138,msg=WM_SYSCOMMAND,wp=0000f060,lp=00000000) 08063178:Call user32.DefWindowProcA(00000138,00000112,0000f060,00000000) ret=0040206c Comments? Changelog: * dlls/ntdll/ntdll.spec Declare the tid debug channel * dlls/ntdll/debugtools.c, relay32/relay386.c, relay32/snoop.c Output the current thread id as the first field if tid is turned on -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ La terre est une bêta...

2 3

Re: [PATCH] Add Callback for wavemapper -> widOpen
by Alexandre Julliard 09 Apr '01

09 Apr '01

"James Hatheway" <james(a)macadamian.com> writes: > I implemented the callback in a very similar way as the Wave out callback > is implemented. You can see this in the functions wodOpen(), wodOpenHelper(), > and WAVEMAP_DstCallback() , look at the data passed in the wom structure > (in dlls/winmm/wavemap/wavemap.c). I don't see any other way that I will > be able to callback into the app when the WineOSS layer notifies the wavemap > layer. The way it is now (wineoss directly calling the app) > causes my app to crash, and doesn't work that way on waveout. But these other functions are not using the WINE_MLD internal winmm structure, so why do you need it in widOpen()? Couldn't you instead do exactly what wodOpen() does? -- Alexandre Julliard julliard(a)winehq.com

3 5

Re: RegSetValueEx problem?
by gerard patel 08 Apr '01

08 Apr '01

At 10:54 AM 08/04/2001 +0100, you wrote: > >I've found time to do some more digging, but I'm still stumped. <snip> I have browsed server/registry.c and it seems that the registry stores a terminating null for strings; so if you have in the registry file a string like "0123456789", it get in memory a length of 11. So I guess that the fix would be to fix the length by -1 somewhere in the path server->ntdll->advapi I have tried this but I am not sure at all this is correct : --- registry.c.orig Mon Mar 5 20:34:21 2001 +++ registry.c Sun Apr 8 18:11:39 2001 @@ -799,14 +799,17 @@ struct key_value *value; int index; size_t ret = 0; + size_t l; if ((value = find_value( key, name, &index ))) { *type = value->type; - *len = value->len; - if (value->data && offset < value->len) + l = value->len; + if ((value->type == REG_SZ) && l) l--; + *len = l; + if (value->data && offset < l) { - if (maxlen > value->len - offset) maxlen = value->len - offset; + if (maxlen > l - offset) maxlen = l - offset; memcpy( data, (char *)value->data + offset, maxlen ); ret = maxlen; } Gerard

2 1

Wrc question
by gerard patel 08 Apr '01

08 Apr '01

I have looked at wrc code and there is a strange 100K limit on the size of mem allocation : assert(size > 0); assert(size < 102400); res = malloc(size); if(res == NULL) { Baffling code - hardcoded limit hidden in a C file :-/ I removed the assert and wrc was able to handle a 1 megabyte bitmap. Anyone has an idea about the meaning of this limit ? Gerard

2 1

Re: debugger startup
by gerard patel 08 Apr '01

08 Apr '01

At 06:32 PM 07/04/2001 +0200, you wrote: <snip> >the setup was that the AeDebug registry key pointed to a shell script, >which in turn, >launched the real debugger (used to set up different context options, >and such) ah that was the problem ? from the bug reports on the news group I had the idea that the key was just not initialized. <snip> >either we decide that shell scripts shouldn't be used (easy solution) The script has an utility, no ? I don't know what it's doing, is the goal to configure the debugger options ? (if yes, maybe using an environment variable could give the same result ??) Gerard

1 0

Re: RegSetValueEx problem?
by davep 08 Apr '01

08 Apr '01

On Sun, 01 Apr 2001, you wrote: > At 01:59 PM 31/03/2001 +0100, you wrote: > > <snip> > >Compiling and running Winemine under Windows 95 this problem doesn't occur. > >Win95 truncates the value at the first null. > > Under NT4 SP6, if I write (for example) '47' + 0 + 13 bytes of garbage, I get > exactly that when querying with the same buffer length (16). > If I use a longer buffer, one binary 0 is appended. > If I use a shorter buffer, nothing is copied and the function does not succeed > (ERROR_MORE_DATA). > > Of course under Regedit the garbage is not displayed; regedit displays only '47' > in this case. I've found time to do some more digging, but I'm still stumped. This is the trace from WineMine saving one parameter in the registry (-debugmsg +relay,+reg): Call advapi32.248: RegSetValueExA(00000038,4038cae0 "Xpos",00000000,00000001,405e66a0,00000010) ret=40388dc8 fs=008f Call kernel32.643: MultiByteToWideChar(00000000,00000000,405e66a0 "3",00000010,00000000,00000000) ret=407c4fe9 fs=008f Ret kernel32.643: MultiByteToWideChar() retval=00000010 ret=407c4fe9 fs=008f Call kernel32.553: HeapAlloc(40390000,00000000,00000020) ret=407c4fff fs=008f Ret kernel32.553: HeapAlloc() retval=403d62fc ret=407c4fff fs=008f Call kernel32.643: MultiByteToWideChar(00000000,00000000,405e66a0 "3",00000010,403d62fc,00000010) ret=407c5023 fs=008f Ret kernel32.643: MultiByteToWideChar() retval=00000010 ret=407c5023 fs=008f Call ntdll.419: RtlInitAnsiString(405e658c,4038cae0 "Xpos") ret=407c5038 fs=008f Ret ntdll.419: RtlInitAnsiString() retval=00000000 ret=407c5038 fs=008f Call ntdll.281: RtlAnsiStringToUnicodeString(40113578,405e658c,00000000) ret=407c504d fs=008f Ret ntdll.281: RtlAnsiStringToUnicodeString() retval=00000000 ret=407c504d fs=008f Call ntdll.230: NtSetValueKey(00000038,40113578,00000000,00000001,403d62fc,00000020) ret=407c5067 fs=008f trace:reg:NtSetValueKey (0x38,L"Xpos",1,0x403d62fc,32) Ret ntdll.230: NtSetValueKey() retval=00000000 ret=407c5067 fs=008f Call kernel32.559: HeapFree(40390000,00000000,403d62fc) ret=407c5083 fs=008f Ret kernel32.559: HeapFree() retval=00000001 ret=407c5083 fs=008f Call ntdll.466: RtlNtStatusToDosError(00000000) ret=407c5089 fs=008f Ret ntdll.466: RtlNtStatusToDosError() retval=00000000 ret=407c5089 fs=008f Ret advapi32.248: RegSetValueExA() retval=00000000 ret=40388dc8 fs=008f So the 16-byte buffer (containing the character "3", a null, and 14 bytes of garbage) has been converted into a 32-byte unicode string and saved. Good. Inside the registry this looks like: "Xpos"="3\0\0\0`\x00ca7@\0\0\0\0\0\0\0@" Now if we read that value back in this is what happens: Call advapi32.236: RegQueryValueExA(00000034,4038cae0 "Xpos",00000000,405e6970,405e697c,405e6974) ret=40388a38 fs=008f trace:reg:RegQueryValueExA (0x34,"Xpos",(nil),0x405e6970,0x405e697c,0x405e6974=16) Call ntdll.419: RtlInitAnsiString(405e6764,4038cae0 "Xpos") ret=407c5565 fs=008f Ret ntdll.419: RtlInitAnsiString() retval=00000000 ret=407c5565 fs=008f Call ntdll.281: RtlAnsiStringToUnicodeString(40113578,405e6764,00000000) ret=407c557a fs=008f Ret ntdll.281: RtlAnsiStringToUnicodeString() retval=00000000 ret=407c557a fs=008f Call ntdll.177: NtQueryValueKey(00000034,40113578,00000002,405e676c,00000100,405e6760) ret=407c55b0 fs=008f trace:reg:NtQueryValueKey (0x34,L"Xpos",2,0x405e676c,256) Ret ntdll.177: NtQueryValueKey() retval=00000000 ret=407c55b0 fs=008f Call kernel32.889: WideCharToMultiByte(00000000,00000000,405e6778 L"3",00000011,00000000,00000000,00000000,00000000) ret=407c56c9 fs=008f Ret kernel32.889: WideCharToMultiByte() retval=00000011 ret=407c56c9 fs=008f Call ntdll.466: RtlNtStatusToDosError(80000005) ret=407c57be fs=008f Ret ntdll.466: RtlNtStatusToDosError() retval=000000ea ret=407c57be fs=008f Ret advapi32.236: RegQueryValueExA() retval=000000ea ret=40388a38 fs=008f RegQueryValueEx maintains that there are 17 characters and since they won't fit in the buffer the function aborts. Incidentally, the "null-terminate if the user forgot" trick is carried out both in RegSetValueEx *and* RegQueryValueEx. Would not once be enough? -- Dave Pickles

1 0

debugger startup
by eric pouech 07 Apr '01

07 Apr '01

someone (IIRC Gérard) had issues when starting the debugger when an exception occured. the setup was that the AeDebug registry key pointed to a shell script, which in turn, launched the real debugger (used to set up different context options, and such) however, what happens is: - the main program (the one generating the exception) tries to launch the debugger using the AeDebug - the process creation forks, and exec:s the debugger program - at the unix level, the debugged program starts, which runs the shell script, which then starts the debugger - at the windows level, since the shell script isn't a Wine process, the call fails (even if an Unix process is created) - the exception handler then reports the error in process creation and stops the main program, whereas the debugger has been started for this program either we decide that shell scripts shouldn't be used (easy solution) or we could do something like : - if the CreateProcess fails, then wait for a certain amount of time. If after that time the current process isn't currently debugged, then report the error. Otherwise assume what did happen is what has been described above comments are welcome A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

1 0

Re: [PATCH] deferred trace
by Alexandre Julliard 07 Apr '01

07 Apr '01

eric pouech <eric.pouech(a)wanadoo.fr> writes: > using the Wine debugger (or any program using the debugging API) may > have some drawbacks. As the API is designed, it's not possible to > get control of the debugged program between its creation and its > entry point entering this makes very difficult to let the Wine > debugger trigger the expected features by poking the memory in the > debuggee. That's not exactly correct, the debugger can intercept the dll loads and break in the dll init code. Since with dll separation all Wine inits will be done inside dlls, the debugger should be able to intercept everything from the point we connect to the wineserver. -- Alexandre Julliard julliard(a)winehq.com

2 1

Re: Nasty Wine/kernel bug, anyone?
by Ulrich Weigand 06 Apr '01

06 Apr '01

> If I were going to make more WAGs (Wild Assed guesses), > I'd hazard a guess that this was due to my Alsa sound system > (running on the AC97 codec on my Asus motherboard). > > I tried to walk the stack back, but didn't get very far > (after the first time of wrongly computing the hex offset > from a .s file, I gave off, stomped off to look > for a better disassembler and gave up). If you have the 'vmlinux' file, try objdump --disassemble vmlinux > My best guess is that we're coming through dentry_open > (xc012e7fe)/ chrdev_open (0xc012f66c) > /soundcore_open (0xc01bbf71). However, I wasn't > seeing a familiar EBP/EIP pattern, so I'm possibly just > pulling random symbols out of the air. Yes, this appears to the proper trace: c0108d7f system_call c012ea2c sys_open c012e732 filp_open c012e7fe dentry_open c012f66c chrdev_open c01bbf71 soundcore_open d0826a42 <module> d087ce3e <module> c0107aa4 __down_failed c010794f __down ........ schedule [I am assuming that you have 256MB main memory. Correct?] Now, the question is still, who is sleeping on that semaphore and why? >From the call trace, it would seem that some sound-related module is loaded, which does a down() on some semaphore in its open() routine. We even know which semaphore: cff267ac. (This does not help much, as this is would appear to be somewhere in kmalloc()ed memory ...) We can continue to track in two directions. First, we can try to locate the point within the Wine application where the open() syscall is performed. >From the trace we see that the system call instruction is located at 40303a24, and the stack pointer points to 405c6638. The system call itself is an open( 41610240, O_WRONLY|O_NDELAY ) [The stack pointer value is rather weird, I'd say ...] This particular open mode occurs in the Wine source only in dlls/winmm/wineoss/audio.c, which confirms the sound hypothesis. The next time you reproduce the bug, could you please add the output of /proc/<pid>/maps for the hanging Wine process? This way, we could further analyse these pointers to Wine user space ... The more promising way to track the problem, however, is to find out which module those d* addresses above reside in. If the modules are still loaded, the output of /proc/ksyms should at least give a hint. For a more refined symbol lookup, it is best to use the 'ksymoops' tool, which correlates the /proc/ksyms output with the ELF symbols read from the object modules themselves. To do so, write this: Call Trace: [<d0826a42>] [<d087ce3e>] to a file and pipe the file through ksymoops. In any case, this would seem to be clearly a bug in that sound module. I don't know, however, why only Wine would trigger that bug ... Bye, Ulrich -- Dr. Ulrich Weigand weigand(a)informatik.uni-erlangen.de

2 1

Re: [PATCH] Name Thread Exception support in Wine debugger
by eric pouech 06 Apr '01

06 Apr '01

James Hatheway wrote: > > Hi guys, > > As I mentioned in an earlier email to the Devel mailing list, I discovered the > application I am supporting started raising more exceptions than usual. These > turned out to be an undocumented signal to the MS VC6 debugger to name the > current thread. You can read more about this at: > http://www.vcdj.com/upload/free/features/vcdj/2001/03mar01/et0103/et0103.asp > or searching google.com or deja.com for "0x406D1388". This patch fixes > the WINE debugger to handle this exception, just like MS VC6 debugger does. something seems wrong in your patch... the szName field from the exception field is never copied from the debugged program space to the debugger space (only the address is) so, you should use ReadProcessMemory instead (something like ReadProcessMemory(pThread->name, sizeof(pThread->name), DEBUG_CurrThread->process->handle, pThreadName->szName); ) also, I don't like the fact that you put the #define in a public header file and the exception struct definition inside the file it would make more sense to me if both were either public or private (I'd go for private, since those values don't seem to be defined in Windows' standard headers) A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

2 1

WWN
by eric pouech 06 Apr '01

06 Apr '01

for personal reasons, I will no longer be able to write the WWN (and I haven't in the last couple of weeks) so, if someone wishes to take the job over, I'd be happy to help him (her) to set it up A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

1 0

Re: [PATCH] deferred trace
by gerard patel 06 Apr '01

06 Apr '01

At 03:00 PM 14/03/2001 -0800, you wrote: <snip> >that the wine debugger can resolve, it is possible to meet the needs that >have been expressed. Expressed ? What I wanted is something short and simple, so I could help people on the news group. The use of my patch could be explained in *one* line and it would have worked with Wine right 'out of the box' :-)... something the internal debugger does not do anymore since a long time. I am afraid that this thing will be more complex to setup and to use that the debugger - something already too complex for many people. And well, I almost never use the debugger myself because it crashes at the slightest provocation so I don't feel much about saying people to use it. So in short, after all my 'needs' (helping ppl on the news group) are indeed specific :-) Gerard

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel