Hello,
I have the first phases of process debugging working under VSTa.
I can dynamically attach to a process, select when it'll break and talk
with the debugger, and examine his memory. If the debugger dies, the
child correctly clears himself out of the debugging state, and continues.
This weekend, I'll start playing with single stepping and breakpoints.
The kernel code for these is written, but not yet exercised.
The debug interface is not ptrace()-ish at all. ptrace() is only
used to pick a process and attach. Using ptrace(), you indicate a port
name; the child (debugged) process connects and communicates using the
usual VSTa messaging techniques. Thus, I get to leverage all the existing
code for handling race conditions, multiple threads, and dying processes.
The debugger, while talking to the child, merely acts as a server receiving
messages and sending responses.
Andy
Received on Thu Dec 9 08:00:43 1993
This archive was generated by hypermail 2.1.8 : Wed Sep 21 2005 - 21:01:53 PDT