![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Now real stuff comes:
After weird setup experience I need to do a real work: set a breakpoint on an undocumented windows kernel API function.
Windbg then. OK, when running windbg locally one can't use breakpoints. OK, remote then. On host, modern Visual studio only supports remote debugging over ip. But Windows 7 target does not. Ok, windbg host then. Remaining connectivity options are FireWire, USB and COM. There is no Firewire on target. There is no COM on target. COM over USB won't work because :).
That is it folks. All one should know about Windows driver/kernel debugging.
After weird setup experience I need to do a real work: set a breakpoint on an undocumented windows kernel API function.
Windbg then. OK, when running windbg locally one can't use breakpoints. OK, remote then. On host, modern Visual studio only supports remote debugging over ip. But Windows 7 target does not. Ok, windbg host then. Remaining connectivity options are FireWire, USB and COM. There is no Firewire on target. There is no COM on target. COM over USB won't work because :).
That is it folks. All one should know about Windows driver/kernel debugging.
