Solved

windows NT kernel driver debugging

Posted on 1997-05-16
4
592 Views
Last Modified: 2013-12-03
 I am having trouble using Windbg to debug a windows nt device driver. I  have a null modem cable installed between two computers both running the  same version of windows nt. I can use the com ports to talk between the
  two so I know the wiring is right. The host uses COM1 the target  COM2.
 
  I have enabled debugging on the target by inserting the /DEBUGPORT=COM2
  and /BAUDRATE=19200 in the boot.ini file under the correct [operating   systems] section.
 
  I start Windbg on the host system by: WinDbg -k i386 COM1 19200.
  When I select go I get the following message:
  Thread Create:  Process=0, Thread=0
  Kernel debugger waiting to connect on com1 @ 19200 baud
  >
 check the SYMBOLS path in WinDbg. It points to a directory with the following structure:

SYMBOLS
    DLL
    EXE
    SYS
The SYS directory contains the checked version of my driver.
 
 I then boot the target and the blue screen comes up saying  Kernel Debugger Using: COM2 (Port 0x2f8, Baud Rate 19200)
The screen flickers and I see the RCV and SND flash.
 
 
 I get stuck here because I never seem to get a response from the target. If I hit the ^C on the host the target will lock up. I never get any message saying the computers connected, but the ^c stops the target. The host never seems to connect!

 What am I doing wrong? Have I left
0
Comment
Question by:rgardea
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 

Expert Comment

by:21186
ID: 1397397
I have been unable to reproduce your symptoms. The message about checking your SYMBOLS path is not normal however. Make sure that the Symbol Search Path under the menu selections "Options\User DLLs" is set to the path you have placed your drivers checked binarie. I did find that if I have this path set wrong and the target machine hits a breakpoint in a driver it cannot continue the boot process, but it will halt on a ^c. After executing a ^c try typing ".reload" in the command window to see what happens.By the way windbg sucks. The only thing it is better than is nothing, wich is your only other option.
0
 
LVL 2

Accepted Solution

by:
amartin030297 earned 100 total points
ID: 1397398
Since nobody has answered you (and I don't have a technical ANSWER for you), but I have a non-free solution:

Purchase SoftIce.  www.numega.com

Its trivial to debug kernel level drivers with it.  And you can
use a serial link OR 2 video cards OR 1 video card and 1 mono monitor (which is how most people do it).

It can also trace into and outof Interrupt (WinDbg sucks at that).

  -- Aaron

0
 
LVL 3

Expert Comment

by:vinniew
ID: 1397399
It would be reasonably trivial to set up a Linux partition for the COM port.  Then you could use tcpdump to get all the info you could ever want.  Reboot. switch back to windows.  done.  Linux is *much* better at getting port info.
0
 
LVL 3

Expert Comment

by:vinniew
ID: 1397400
Did I say tcpdump? whoops.  redirect a tty to a file.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

With most software applications trying to cater to multiple user needs nowadays, the focus is to make them as configurable as possible. For e.g., when creating Silverlight applications which will connect to WCF services, the service end point usuall…
For most people, the WrapPanel seems like a magic when they switch from WinForms to WPF. Most of us will think that the code that is used to write a control like that would be difficult. However, most of the work is done by the WPF engine, and the W…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question