BUG: Unable to Hit Breakpoint on ELSE IF Statement

• The Microsoft C/C++ Compiler (CL.EXE) included with: - Microsoft C for MS-DOS, versions 6.0, 6.0a, and 6.0ax - Microsoft C/C++ for MS-DOS, version 7.0 - Microsoft Visual C++ for Windows, versions 1.0 and 1.5 - Microsoft Visual C++, 32-bit Edition, versions 1.0, 2.0, 2.1, 4.0,

       4.1, 4.2, 5.0
  

SYMPTOMS

If the sample code in the "MORE INFORMATION" section, below, is compiled for debugging (/Zi), the debugger (either CodeView or the Visual Workbench) does not stop at a breakpoint that is placed on the ELSE IF statement.

CAUSE

The compiler does not generate the correct symbolic information for the line of code containing the ELSE IF statement.

RESOLUTION

To work around the problem, place the "else" and "if" statements on separate lines. For example:

   else
      if (i==7)

STATUS

Microsoft has confirmed this to be a bug in the products listed at the top of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

To reproduce this problem with the sample code below:

1. Set a breakpoint on the line with the ELSE IF statement

2. Press F5(GO) to start debugging the program.

In CodeView, if you switch into mixed source/assembly mode, you can verify that there is executable code associated with the ELSE IF statement. If a breakpoint is placed on one of the lines of assembly code for the ELSE IF statement and the application is debugged, the code stops running at the breakpoint. With the Visual Workbench debugger, step through the code at the ELSE IF statement to set the breakpoint.

Sample Code

/* Compile options needed: /Zi /Od
*/

   void main(void)
   {
      int i=100;
      if (i==2);
      else if(i==7);  /* cannot stop on this line */
   }