[Wine] Re: Windows Kernel & Executive implementation

Stefan Dösinger stefandoesinger at gmx.at
Wed Feb 27 15:10:28 CST 2008

Am Mittwoch, 27. Februar 2008 21:18:28 schrieb richardvoigt at gmail.com:
> What is your preferred utility for
> filling that niche (logging I/O calls)?
I never needed that; All I am logging are d3d calls, there I am using PixWin 
or simple wine logs, and bugle or the apple opengl profiler on the gl side.

> Those particular apps are useful to the point that every competent
> Windows sysadmin knows of them.
Ya, but do you expect the Windows tools to be able profile Linux processes, 
and know about Linux syscalls, etc? So all you could use them for is auditing 
Windows processes inside Wine. They are Windows system utilities and thus 
tied to the Windows API. Trying to use them on Wine is similar to trying to 
use sudo in mingw on Windows, or trying to check an NTFS partition with 
e2fsck. Running Windows system tools is way beyond the scope of Wine IMHO.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20080227/234b2c35/attachment.pgp 

More information about the wine-devel mailing list