Why would one do the ugly way rather than use LiveKD from the Inside
Windows 2000 book or use LocalKD with Windbg on WinXP?
For anyone unfamilar with these they are “local machine debugging”
things that basicly allow you to read/write memory, run some extensions
and such. Things like stacktrace, breakpoints and debug output don’t
work with them. Kind of a cross between a dump file and a live machine.
-----Original Message-----
From: xxxxx@starband.net [mailto:xxxxx@starband.net]
Sent: Monday, February 04, 2002 9:45 AM
To: Kernel Debugging Interest List
Subject: [windbg] Re:How to do kernel debugging with only one PC?
Easiest way:
There is a utility called ‘debugview’ that lets you see the debug output
on
the console on the local PC. It’s downloadable, I believe. I think it
might
have also come with Walter Oney’s Essential WDM Driver book (since it’s
basically the only one!) as well. See if it’s on Sysinternals.com?
Ugly Way:
The other thing you can do is (like we used to have to) roll your own
kernel debugger or at least most of what you need it for, at the expense
of lots of time.
Create a kernel driver that you can read/write data to that
has some means of storing data. (IOCTL interface)
Make a .dll that lets you call functions that write into the memory set
up by this kernel debug driver. Then make a user app that lets you
read/write to this driver, getting data.
Basically re-writing your own version of soft-ice, only one that’s
easier to write because you’re using the debug statements manually and
not trying to hook the OS. In your driver you could thus write to this
space.
Soft-Ice:
It’s a matter of the cost of your time vs. the cost of something like
soft-ice, which is pricey but not unreasonable given the work that went
into it.
If you can get soft-ice to work that is! I have it and
have run into regular blocking points where it doesn’t
work on a given target machine, and basically
decided that for now the time spent trying to get it to
work was more expensive than carrying around two machines
to do development/debugging on with WinDBG (current project).
I’m also a bit more practiced with WinDBG than soft-ice lately.
There were times it failed that I really wanted it to
work. There have been times when it’s been great and
solved problems that were much more difficult with WinDBG.
You are currently subscribed to windbg as: xxxxx@microsoft.com To
unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to windbg as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-windbg-$subst(‘Recip.MemberIDChar’)@lists.osr.com