If you’re just getting started with WinDBG, you definitely want to read
the docs that come with the latest version from
http://www.microsoft.com/ddk/debugging … The section called “Installation
and Setup” will probably answer 99% of your questions as far as the setup
for WinDBG goes… the docs for WinDBG are very thorough… there’s also a
section called “Debugging Service Applications with WinDbg” that you may
find useful…
Also, if you have WinDBG hooked up to the system in a kernel-mode
debugging setup, any user-mode debug output from the target will be shown
on the host computer (that is if you don’t have a debugger running the
user-mode code on the target)…
Sorry to just say RTFM, but it’s really complete and helpful :sean
Michael Jackson wrote:
If you’ll allow that the only stupid question is the on not asked…
I have a service that runs at startup. It is tightly tied to my
protocol driver. I’d like to look at a problem with the startup of its
logging subsystem. I’m used to SoftIce so I don’t have the correct
mindset for using windbg in this situation. I need some pointers.I assume I use NTSD on the target machine and control it via windbg on
my host?How do I start NTSD before my service?
What else do I need to know to get started?
Thanks for listening.
Michael S. Jackson
NetMotion Wireless, Inc.
xxxxx@nmwco.com
You are currently subscribed to windbg as: xxxxx@stg.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