Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

WinDbg hanging

OSR_Community_UserOSR_Community_User Member Posts: 110,217
Hello,

i am using build 2195 of Win2000 on both systems. WinDbg will not
attach. it just says
"Kernel debugger waiting to connect on com1 @ 19200 baud"

I have tried the following versions of windbg
2156.1 (RC3)
2184.1 (On Win2000 Customer support CD)
2195.1 (On DDK)
2195.10 (Downloaded)

None of them will get past that stage. These systems use to work when
running the betas of Win2000.
i386kd.exe does connect but it doesnt appear to work with source code very
well.

Does anyone have any suggestions?
Machine A:
Intel 333 Pentium II
Com 1
Machine B
Intel Dual Processor Pentium II 400 (Running MPS kernel)
Com 2

Rob

Comments

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I am using the Windbg that came on the customer support disk. At 19200 the
    target machine doesn't stop and wait for the debugger. It just boots up.
    However, if I use a 38400 connect speed, the target machine will stop after
    filling in the character mode progress bar on the black screen. The
    debugger should already be waiting on the com port at 38400. I issue a
    Ctrl-C from the debugger with the caret/focus in Windbg's command window.
    The two machines synchronize and the debugging begins. I am not sure if
    this is how Windbg is supposed to work (it didn't do this for me under NT
    4) or it is a symptom of my less than stable hardware that I am developing
    for. Also, I had very little success until I started launching Windbg with
    the -w I found I had to launch Windbg, setup the
    debugging parameters, save them to a workspace name, and exit.

    Best of luck.

    Regards,
    Robert Saccone
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Internals & Software Drivers 15 November 2021 Live, Online
Writing WDF Drivers TBD Live, Online
Developing Minifilters 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online