Re: [Valgrind-developers] Managing complexity

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

At 19.45 16/08/2004, Adun R. wrote:
>Hold your horses; it seems like you're planning to run atleast part of 
>your code in ring 0.

nope. If you mean the KiXxx functions, despite what the name may suggest, 
they are user-mode functions. They're probably called like that because 
only the kernel calls them. No, what a session of Valgrind for Windows 
would look like is:
  - run the client as a debuggee
  - place breakpoints on the KiXxx callbacks
  - initialize the shadow state (virtual memory, etc.) with the client's 
current state
  - execute the client's code in the Valgrind process, leaving the client's 
threads suspended until they perform a system call