Compiling and Linking Your Program

Before using the debugger, you need to compile and link your program.

For VACPP programs, use the following options:

• Ti+
  Compiles your program to produce an object file that includes line number information and a symbol table in addition to the source code.
  /O-
  Compiles your program with optimization off. This is the default.
  /Oi-
  Compiles your program with inlining off. This is the default.
  /DEbug
  Links your program to produce an executable file that includes line number information and a symbol table in addition to the executable code.

  Note: When you specify the /Ti+ option with the /DEbug option, icc passes this option to the linker automatically, so you only need to use it if you link separately from the compile.

  For more information about compiling and linking your program, refer to IBM C++ Tools Programming Guide.

  For Microsoft CL, CL386, MASM, and MASM386 programs, use the following options:

• Zi
  Compiles your program to produce an object file that includes line number information and a symbol table, in addition to the source code.
  /Od
  Compiles your program with optimization off.
  /CO
  Links your program to produce an executable file that includes line number information and a symbol table in addition to the executable code.

  For Watcom wpp386 programs, use the following options:

• d2
  Compiles your program with full debugging information.
  -hc
  Compiles your program emitting CodeView debug format (currently, the debugger only supports Watcom's CodeView debug format).
  -od
  Compiles your program with optimization off.

  For the Watcom linker, wlink, use this option:

  d codeview

  Links your program with CodeView debug format.

  The debugger supports a separate debug file (from your created application) for the Watcom compiler. For the Watcom linker, wlink, use this option to create a separate debug file if desired:

  op symf

  This will create a .sym file. Be careful not to confuse this file with a KDB .sym file. The debugger looks for debug information first in the application file. If it doesn't find it, it looks for the debug information in a .dbg file and then in a .sym file as a last resort. Most users rename the separate Watcom .sym file to a .dbg file.

  ---

  [Back: Software Requirements]
  [Next: Setting Environment Variables]