Changes between Version 2 and Version 3 of DebuggingAndSuch


Ignore:
Timestamp:
May 22, 2007, 11:40:44 PM (18 years ago)
Author:
stevenhl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DebuggingAndSuch

    v2 v3  
    1010}}}
    1111
    12 It appears that the logs are clears by the copy.
     12It appears that the logs are cleared by the copy.
    1313
    1414
    … …  
    2121== The Kernel Debugger ==
    2222
    23 There are times when you just has to watch the code execute to understand the issue.  The kernel debugger can help here.  You and second system and either a serial port to or a supported NIC to use the debugger.  You can not use a NIC for debugging driver initialization and such.  Not enough to the OS is loaded.  However, NIC debugging can make working other areas of driver operation go faster.
     23There are times when you just has to watch the code execute to understand the issue.  The kernel debugger can help here.  You need a second system and either a serial port to or a supported NIC to use the debugger.  You can not use a NIC for debugging driver initialization and such.  Not enough of the OS is loaded.  However, NIC debugging can make working other areas of driver operation go faster.
    2424
    25 The kernel debugger comes in two flavors.  There's the traditional command line debugger.  There's the ICAT source level GUI debugger.  Which is best depends on which part of the driver code you are working on.  The source level debugging is handy, but it can be slow over a serial port.
     25The kernel debugger comes in two flavors.  There's the traditional command line debugger and there's the ICAT source level GUI debugger.  Which is best depends on which part of the driver code you are working on.  The source level debugging is handy, but it can be slow over a serial port.
    2626
    2727More to come...