Re: WORKING_SET.COM gives all COM states when run at high priority

prep_at_prep.synonet.com
Date: 06/30/05 

Date: Thu, 30 Jun 2005 23:32:00 +0800

"AEF" <spamsink2001@yahoo.com> writes:

> David B Sneddon - bigpond wrote:

>> Does $GETJPI not operate within the context of the process you want
>> the information about? In which case that process would need to
>> "run" to return the information...

> I don't see how this can be. If $getjpi ran in the target process's
> context, wouldn't its result go into a symbol in that target process
> and screw it up? Also, if the target process needs to run $getjpi
> than I'd expect to see processes all show up as CUR, since they are
> running as you say.

The getjpi does a kernel AST into the target process and runs within that
process, get the data, then ASTs back to the sender. Most of the work is in
the target process context, not the inquirers. 

-- 
Paul Repacholi                               1 Crescent Rd.,
+61 (08) 9257-1001                           Kalamunda.
                                             West Australia 6076
comp.os.vms,- The Older, Grumpier Slashdot
Raw, Cooked or Well-done, it's all half baked.
EPIC, The Architecture of the future, always has been, always will be.

Relevant Pages

  • Re: WORKING_SET.COM gives all COM states when run at high priority
    ... Why are they waiting for the CPU? ... If $getjpi ran in the target process's ... context, wouldn't its result go into a symbol in that target process ... if the target process needs to run $getjpi than ...
    (comp.os.vms)
  • Re: WORKING_SET.COM gives all COM states when run at high priority
    ... If $getjpi ran in the target process's ... > context, wouldn't its result go into a symbol in that target process ... if the target process needs to run $getjpi than ... It wont be CUR because you are the process that has commanded the operation ...
    (comp.os.vms)
  • Re: Injected DLL causes process termination - occasionally
    ... I would recommend debugging the child process in order to get a better feel for why your attempt is failing. ... // Allocate memory in the target process ... pWriteBuffer = VirtualAllocEx(pi.hProcess, pWriteBuffer, ... // Change the execution context of the the primary thread of the ...
    (microsoft.public.win32.programmer.kernel)
  • Injected DLL causes process termination - occasionally
    ... My injected code is indeed called, ... // Allocate memory in the target process ... pWriteBuffer = VirtualAllocEx(pi.hProcess, pWriteBuffer, ... // Change the execution context of the the primary thread of the ...
    (microsoft.public.win32.programmer.kernel)