i used Local Kd for Attachkernel and WriteDumpFile in the example
code i posted in the other thread
now out of curiosity i tried Attaching to a VirtualPc instance over a named pipe
using
status = g_Client->AttachKernel(
DEBUG_ATTACH_KERNEL_CONNECTION,
“com:pipe,port=\\.\pipe\debugPipe,resets=0,reconnect”
);
i can attach to the kernel but WaitForEvent after this doesnt get signalled
and i had to force a DebugBreak() in the target
for my WriteDumpFile() to Execute
is there an api to send breakin from my exe or is there some steps to follow
and how to resume the kernel after WriteDumpFile() is done
i tried
g_Control->SetExecutionStatus (
DEBUG_STATUS_GO
);
but the target kernel doesnt seem to get it and remains freezed
whereas in windbg issuing a g works
kd> .dump /m /a /u “c:\bytre.dmp”
Creating c:\bytre_0d7c_2012-07-13_18-46-56-187_f0f0.dmp - mini kernel dump
Dump successfully written
kd> g
there isnt much difference in the dumps though (about 500 bytes differ
between windbg.dump /m /a /u and my WriteDumpFile whose sizes are
identical
13/07/2012 18:48 131,072 kohlyang_test.dmp
Directory of c:\
13/07/2012 18:47 131,072 bytre_0d7c_2012-07-13_18-46-56-187_f0f0.dmp