hi, i forgot the other subject want to write;
Connection steps for remote kernel debug of mine;
-connect the two pc via null-modem cable
-open the WinDbg on host pc
-Select Kernel Debug (COM)
There is nothing except the log below;
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \.\com1
Waiting to reconnect…
Whenever i restart the target pc, host pc connect the target one. (1)
After i open the app on target pc(i know that this movement cause the BSOD), windbg shows the error logs but target pc freezing, u can not do anything without shutdown by button(2)
(1) and (2), are they normal?
Not : os_host_pc : win xp 32 bit
os_target_pc: win 7 64 bit
xxxxx@netas.com.tr wrote:
hi, i forgot the other subject want to write;
Connection steps for remote kernel debug of mine;
-connect the two pc via null-modem cable
-open the WinDbg on host pc
-Select Kernel Debug (COM)
There is nothing except the log below;
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \.\com1
Waiting to reconnect…
Whenever i restart the target pc, host pc connect the target one. (1)
Right. Is there something about that that seems unusual to you?
After i open the app on target pc(i know that this movement cause the BSOD), windbg shows the error logs but target pc freezing, u can not do anything without shutdown by button(2)
I can’t imagine what else you would be expecting here. You have a fatal
system error. The operating system is halted. If the kernel debugger
were not attached, the computer would be dead, until a power cycle. The
debugger does, at least, allow you to poke around in the dead system to
find out what is at stake, but the system is still dead.
You can, however, enter the .reboot command to restart the target,
instead of using the power button.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.