This section covers problems related to setting and clearing breakpoints.

Some statements don't have dashes in the Breakpoint column, making it impossible to set them.

The CodeWarrior linkers do not generate symbolics information for source code that is not linked into the final output file. If a statement is never actually used, the linker does not include it in the final object code. You cannot set a breakpoint on such a statement, because the object code does not exist.

Code optimization may also reorganize the object code extensively, affecting the correspondence between object code and source code and making it difficult or impossible to set breakpoints accurately.

• Make sure all your code is used. Change the source code if necessary.
• Check your source code to see if statements were ignored by the compiler because of compiler directives.
• Disable all compiler optimizations and rebuild your project. Optimization may make changes in object code that do not correspond to your source code. You should get a breakpoint marker at every available statement after disabling optimizations. For more information, see "Impact of optimizing code on breakpoints".
• Use a coding style wherein you place only one statement on a source line. The compiler outputs breakpoint information for multiple statements on a line, but the debugger only displays the current source line. You might step multiple times on the same source line.

I set a breakpoint, but it does not work.

A breakpoint stops execution only if it is reached, it is active, and its condition (if it has one) is true.

• Step through your code to verify whether you reach the statement at which you placed the breakpoint. To learn more, refer to "Setting and clearing breakpoints".
• Look in the Breakpoints window to see if the breakpoint is inactive.
• If the breakpoint has a condition, make sure it evaluates to true. The debugger ignores breakpoints with false conditions. See "Conditional breakpoints" for more information.