Return to readme CVS log

Up to [WindowsNT SDKs] / mstools / samples / deb

Microsoft Windows NT Build 297 06-28-1992

Sample: Demonstration of the Debug API Function

Summary:

The Debug Event Browser (DEB) Win32 SDK sample demonstrates
the new debug API.  This sample acts as a debugger for both
newly created debugee processes or attaches to current
active processes.

DEB is not a debugger in the traditional sense; it is a
browser as its name implies.  DEB displays the debug events,
and their relevant properties, as they happen and invokes
the default handlers supplied either by the debugee or the
system.  Only the minimal debug event handling is imposed
such that the debug events are displayed and the debugee is
continued on its normal course of execution.

The sample is source code compatible for both the Intel
80x86 and MIPS R4000 Windows NT platforms.

More Information:

The following is a complete list files accompanying the
Debug Event Browser sample:

   DEB.BMP        DEB bitmap used by DEB.RTF
   DEB.DEF        DEB module definition file
   DEB.DLG        DEB dialog resource script file
   DEB.H          DEB ID values and user message defines
   DEB.HPJ        DEB help project file
   DEB.ICO        DEB icon
   DEB.RC         DEB resource file
   DEB.RTF        DEB help topic file
   DEBDEBUG.C     DEB debug support functions
   DEBDEBUG.H     DEB debug support functions header
   DEBMAIN.C      DEB main module - WinMain and callbacks
   DEBMAIN.H      DEB main module header
   DEBMISC.C      DEB miscellaneous support functions
   DEBMISC.H      DEB miscellaneous support functions header
   LINKLIST.C     Ordered doubled-linked list library
   LINKLIST.H     Ordered doubled-linked list library header
   MAKEFILE       Make/Nmake file for the entire sample
   README         This file you are presently reading
   TOOLBAR.BMP    Toolbar bitmap used by DEB.RTF
   TOOLBAR.C      Toolbar functions
   TOOLBAR.DEF    Toolbar module definition file
   TOOLBAR.H      Toolbar functions header

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.