RE: [Valgrind-developers] Developing Valgrind for Windows

[KJK::Hyperion <no...@li...>]

At 10.23 02/03/2004, Nicholas Nethercote wrote:
>>>I think that nothing short of a full fork of Valgrind will do
>>I get that feeling too.
>Same here.  Not only does Windows have rather, er, interesting 
>architectural features,

Actually, the kernel is pretty straightforward - Linux 2.6 comes pretty 
close to it in features and architecture. The problem is that the kernel is 
too far from the applications. Example: the socket functions are 
implemented by an user-mode multiplexer, and it's only the *default* 
implementation that processes them in kernel mode, and anyway they get 
there as IOCTLs. This makes it very difficult to validate the use an 
application is making of BSD sockets

>you would be fighting its closedness the whole way.  Sounds like a nightmare.

sounds like real fun, to me :-) but I'm involved in ReactOS 
(<http://reactos.com/>), so I may be biased