C

C++ expression

An expression that can be evaluated by the C++ expression evaluator.

For details of the syntax, see C++ Numbers and Operators.

C call stack

See call stack.

call stack

The set of stack frames for each thread containing representing the function calls made by the thread. Each time a function call is made a new stack frame is pushed onto the top of the stack. When that function returns, the stack frame is popped off the stack.

Sometimes referred to as the C call stack or simply the stack.

callback object

See event callbacks, input callbacks, and output callbacks.

checked build

Two different builds of each NT-based operating system exist:

• The free build (or retail build) of Windows is the end-user version of the operating system. For details, see free build.
• The checked build (or debug build) of Windows serves as a testing and debugging aid in the developing of the operating system and kernel-mode drivers. The checked build contains extra error checking, argument verification, and debugging information that is not available in the free build. , making it easier to trace the cause of problems in system software. A checked system or driver can help isolate and track down driver problems that can cause unpredictable behavior, result in memory leaks, or result in improper device configuration.

Although the checked build provides extra protection, it consumes more memory and disk space than the free build. System and driver performance is slower, because additional code paths are executed due to parameter checking and output of diagnostic messages, and some alternate implementations of kernel functions are used.

The checked build of Windows should not be confused with a driver that has been built in one of the Checked Build Environments of the Windows Driver Kit (WDK).

For more information, see "Using the Checked Build of Windows" in the WDK.

child symbol

A symbol that is contained in another symbol. For example, the symbol for a member in a structure is a child of the symbol for that structure.

See also parent symbol.

For more information, see Scopes and Symbol Groups.

client

See client object.

client object

A client object is used for interaction with the debugger engine. It holds per-client state, and provides implementations for the top-level interfaces in the debugger engine API.

For more information, see Client Objects.

client thread

The thread in which the client object was created. In general, a client's methods may be called only from this thread. The debugger engine uses this thread to make all calls to the callback object registered with the client.

For more information, see Client Objects.

code breakpoint

See software breakpoint.

crash dump file

A file that contains a snapshot of certain memory regions and other data related to an application or operating system. A crash dump file can be stored and then used to debug the application or operating system at a later time.

A user-mode crash dump file can be created by Windows when an application crashes, and a kernel-mode crash dump file can be created by special Windows routines when Windows itself crashes. There are several different types of crash dump files.

For more information, see Crash Dump Files.

current process

The process that the debugger engine is currently controlling. When an event occurs, the current process is set to the event process.

See also current target and current thread.

For more information, see Threads and Processes.

current target

The target that the debugger engine is currently controlling. When an event occurs, the current target is set to the event target.

See also current thread and current process.

current thread

The thread that the debugger engine is currently controlling. When an event occurs, the current thread is set to the event thread.

See also current process and current target.

For more information, see Threads and Processes.