Debugging C++ Programs Using the SAS/C Debugger

Debugging Initialization and Termination

A typical C++ program contains intialization functions in each compilation at program startup, which are called at program startup to initialize static and extern data defined in that compilation. If you want to debug one of these initialization functions, you can set a breakpoint on _ _init_sname , where sname is the sname for that compilation. (See Option Descriptions.) Similarly, a function called _ _term_sname is called for each compilation at termination.

By default, the first function name shown in the Status window is one of these initialization functions. While the debugger is stopped in these functions, you can debug the initialization of static and extern variables. As you step through the initialization functions, each function is in turn shown in the Status window. Note that the initialization and termination functions are not shown in the Source window, as they do not exist in user C++ code.

Note: The functions _ _init_sname and _ _term_sname are implementation-dependent. Either the implementation or the names, or both, may change in a future release. [cautionend]

Bypassing Initialization Functions

If you do not want to debug your program's initialization functions, you can bypass them in one of several ways:

set breakpoints in functions that are of interest and issue a go command
put a Break main entry command in your debugger profile and issue a go command (this causes debugging to begin at the main function)
issue a Runto main entry command from the command line (this causes your program to advance to main ).

Chapter Contents
Previous
Next
Top of Page