process' address space. Usually, a process handle doesn't hold reference to
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
Yes, I realize that the debug events must be handled in the thread that
launched the
process, because that is consistent with the documentation. But the
behavior of
ReadProcessMemory is a little stranger.
What is odd is that when the procress terminates, its memory is still
available in the
thread that was handling debugging. Examining the contents of the process
(which actually
takes over a minute in the real app) works fine in the debugger thread,
but does not work
in another thread. So there are some interesting issues here about the
"liveness" of the
process memory space which appear to be undocumented.
joe
On Wed, 2 May 2007 08:50:27 -0700, "Alexander Grigoriev"
<alegr@earthlink.net> wrote:
Apparently, the debug events are sent through thread-targeted APCs (this
is
why one should not send APC to the debugger thread, as the doc says). I'm
not sure what you mean "until process stops". Are you trying to read/write
memory while the target process is suspended or gone at all?