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

Re: FAQ: best win32 api spy tool?

by Duane Clark

Dan Kegel wrote: > > The SPYXX.EXE in my copy of msvc4.0 appears to only let you log > windows messages, not api calls. Then again, since help doesn't > work under Wine, I can't tell if I'm missing something... > Oops, my mistake. That's right.

Jan. 2, 2003

Re: FAQ: best win32 api spy tool?

by Dan Kegel

Jeremy White wrote: > Hey Dan, > > We've looked into this extensively; looking at both flavors > of apispy (yes, there are two of them, with very similar names), > and a lot of other variations. > > However, I've got a half baked W2K based solution similar to > the Detours library from Microsoft. The advantage to my approach > is that it generates a relay log identical to that of Wine, > which then allows for diffing the log files. > > If you'd like to work on this, this might well be a great > project for you, and I'd be happy to do a brain dump and > transfer the work to you. > > *I* think it would be wicked cool. Sadly, most of the Wine gurus > I work with just shake their head and smile whenever I suggest > it deserves priority. That does sound awesome. Yes, proceed with brain dump, please. Worst case, this will let others work on it even if I fail to make progress. Thanks! - Dan -- Dan Kegel Linux User #78045 http://www.kegel.com

Jan. 2, 2003

Re: Set/WindowLong problem in user/win test

by Alexandre Julliard

Francois Gouget <fgouget(a)free.fr> writes: > This test uses {Get,Set}WindowLongW which of course does not work on > Win9x, thus causing the test to fail. I guess part of the goal is to > check that mixing Ansi calls (CreatewindowExA) with Unicode calls works. No, there's no real reason to use the W call since we only set parent and style. We might as well replace all calls by the A version. > So I wrote a function test_set_window_long function that calls > SetWindowLongW and then SetWindowLongA and checks that their results > match but that causes the test to fail (at least on NT4 and Wine). > More precisely even if all this function does is the following, then the > test fails: > > { > LONG rc=SetWindowLongA(hwnd,nIndex,dwNewLong); > SetWindowLongA(hwnd,nIndex,dwNewLong); > return rc; > } > > Comment out the second SetWindowLongA and it works. Why would calling > SetWindowLong a second time make any difference? The behavior of SetWindowLong(GWL_HWNDPARENT) depends on the current parent, so calling it a second time with the same arguments is not necessarily a nop. -- Alexandre Julliard julliard(a)winehq.com

Jan. 2, 2003

Re: FAQ: best win32 api spy tool?

by Jeremy White

Hey Dan, We've looked into this extensively; looking at both flavors of apispy (yes, there are two of them, with very similar names), and a lot of other variations. However, I've got a half baked W2K based solution similar to the Detours library from Microsoft. The advantage to my approach is that it generates a relay log identical to that of Wine, which then allows for diffing the log files. If you'd like to work on this, this might well be a great project for you, and I'd be happy to do a brain dump and transfer the work to you. *I* think it would be wicked cool. Sadly, most of the Wine gurus I work with just shake their head and smile whenever I suggest it deserves priority. Cheers, Jer On Wed, 2003-01-01 at 17:30, Dan Kegel wrote: > Hi, > I'm trying to figure out why an app works on Windows but not Wine, > and it'd sure be nice to be able to log all the api calls the > app makes under each of the two environments; then perhaps > I could compare the logs to see where Wine differed from Windows. > > Does anyone else do stuff like that? If so, what tools do you use? > > http://www.wheaty.net/FAQ.htm#APISPY32 says that the best tool out there is > http://www.internals.com/utilities_main.htm > (Supposedly the author will send source to you on request, too.) > That program requires a text file containing the prototype for > each API you want to spy on, though, and it only comes with 3 APIs > as an example. Does anyone have a full version of that file, or > a perl script to create it from the wine tree? > > I suppose I could write my own, too, if that's the only way > to get a tool that works well in both environments. > http://help.madshi.net/ApiHookingMethods.htm > seems to have lots of info on that. > > -- > Dan Kegel > Linux User #78045 > http://www.kegel.com >

Jan. 2, 2003

Re: RtlUnicodeStringToInteger prototype missing, and wrong?

by Alexandre Julliard

Francois Gouget <fgouget(a)free.fr> writes: > On Tue, 24 Dec 2002, Dan Kegel wrote: > > > Shouldn't this be declared in wine/include/winternl.h, like > > the other Rtl functions? > > Microsoft does not declare it in winternl.h. We could create an ntddk.h > or a wdm.h header but these are part of the Windows DDK, not the SDK. > I'm not sure we have 'public' DDK headers in Wine. Actually that's what winternl.h is for; Microsoft only lists a few functions in there but we might as well put the others there too. They will probably end up in Microsoft's winternl.h someday, after a few more lawsuits... -- Alexandre Julliard julliard(a)winehq.com

Jan. 2, 2003

Re: winemaker problem

by Hans Christian Studt

Sylvain Petreolle wrote: > Define a drive that can see rhis directory, for example P: as > /user/usr/local/wine/programs/ or move the source directory where it > can be seen by current defined drives in $HOME/.wine/config. > > If you read it, the error message describes exactly what must be > done... > >>When i try to run winemine I get this error >>(/user/usr/local/wine/programs/winemine-hcs) #./winemine-hcs >>winemine-hcs.so >>Warning: could not find wine config [Drive x] entry for >>current working directory >>/user/usr/local/wine/programs/winemine-hcs; starting in >>windows directory. >>/usr/local/bin/wine: cannot find 'winemine-hcs.exe' Thanks. Now I have defined [Drive P] "Path" = "/usr/local/wine/programs" but there is still a problem left (/user/usr/local/wine/programs/winemine-hcs) #./winemine-hcs /usr/local/bin/wine: cannot find 'winemine-hcs.exe' It still cannot find 'winemine-hcs.exe'. What seems to comes nearest is -rwxr-xr-x 969 jan 1 21:00 winemine-hcs -rwxrwxr-x 793446 jan 1 21:00 winemine-hcs.so -rw-rw-r-- 44160 jan 1 21:00 winemine-hcs.spec.c -rw-rw-r-- 92648 jan 1 21:00 winemine-hcs.spec.o -rw-rw-r-- 173 jan 1 20:59 winemine.exe.dbg.c -rw-rw-r-- 2040 jan 1 21:00 winemine.exe.dbg.o -rw-rw-r-- 43665 jan 1 15:39 winemine.exe.spec.c I sure hope someone can help out - because I plan to try to see if I can make some of those 7.000 win32 applications over at sourceforge.net compile under winelib. -- Hans Christian Studt : http://hc.studt.dk mailto:hc(a)studt.dk .dk og W3C standarder : http://w3c.studt.dk

Jan. 2, 2003

Re: __WINE__ vs. __WINESRC__

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > On December 22, 2002 03:04 pm, Francois Gouget wrote: > > But I'm open to change, '__WINE__' looks more like the others. Maybe > > '__WINELIB__' would do? (but I prefer '__WINE__') > > Alexandre, what do you think? I'd like to have winegcc define this by > default, but we have to decide on a symbol name. Sorry to bug you with > this now, but I'd like to get it out of the way so I can properly finish > the wxWindows port. I think __WINE__ is best, let's just rename the internal one. BTW this may be the occasion to clean things up a bit, we have way too many of these ifdefs in our headers, and many of them could be removed IMO. -- Alexandre Julliard julliard(a)winehq.com

Jan. 2, 2003

Re: FAQ: best win32 api spy tool?

by Duane Clark

Dan Kegel wrote: > Hi, > I'm trying to figure out why an app works on Windows but not Wine, > and it'd sure be nice to be able to log all the api calls the > app makes under each of the two environments; then perhaps > I could compare the logs to see where Wine differed from Windows. > > Does anyone else do stuff like that? If so, what tools do you use? You had previously mentioned having a copy of msvc. Did you check in it for SPY++? I would have to say that it seems to work quite well under Wine.

Jan. 2, 2003

Re: Alexandre?

by Alexandre Julliard

"Jeff Smith" <whydoubt(a)hotmail.com> writes: > I've seen no activity on wine-cvs for a week (Dec 23). > What's up? Holiday vacation? Yep, I'm just back from one week without email access; there should be plenty of traffic on wine-cvs soon judging from my mailbox ;-) Happy New Year to everybody! -- Alexandre Julliard julliard(a)winehq.com

Jan. 2, 2003

FAQ: best win32 api spy tool?

by Dan Kegel

Hi, I'm trying to figure out why an app works on Windows but not Wine, and it'd sure be nice to be able to log all the api calls the app makes under each of the two environments; then perhaps I could compare the logs to see where Wine differed from Windows. Does anyone else do stuff like that? If so, what tools do you use? http://www.wheaty.net/FAQ.htm#APISPY32 says that the best tool out there is http://www.internals.com/utilities_main.htm (Supposedly the author will send source to you on request, too.) That program requires a text file containing the prototype for each API you want to spy on, though, and it only comes with 3 APIs as an example. Does anyone have a full version of that file, or a perl script to create it from the wine tree? I suppose I could write my own, too, if that's the only way to get a tool that works well in both environments. http://help.madshi.net/ApiHookingMethods.htm seems to have lots of info on that. -- Dan Kegel Linux User #78045 http://www.kegel.com

Jan. 1, 2003