BUG: Conditional Breakpoint with Pass Count Breaks Incorrectly

Last reviewed: July 22, 1997
Article ID: Q116461
4.00 4.01 4.10 MS-DOS kbtool kbcode kbbuglist

The information in this article applies to:

  • Microsoft CodeView for MS-DOS, versions 4.0, 4.01, and 4.1

SYMPTOMS

When using conditional breakpoints with a pass count in CodeView for MS-DOS, CodeView may initially break at the wrong time.

RESOLUTION

To work around the problem, run your program beyond the point where the variables in the expression are declared or initialized; then set the conditional breakpoint and resume the program.

STATUS

Microsoft has confirmed this to be a bug in CodeView for MS-DOS, versions 4.0, 4.01, and 4.1. We are researching the problem and will post new information in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The sample program below demonstrates this problem. Build a debug version, load it into CodeView for MS-DOS, and then type the following commands in the CodeView command window:

   >bp ?{main}j>2 /p4
   >g
   >g

The first g command stops before i and j are initialized; the second g command stops at the proper breakpoint location.

Sample Code

/* Compile options needed:   /Zi
*/

   int a[10][10] = {0};

   void main( void )
   {
       int i, j;

       for ( i = 0; i < 10; i++ )
           for ( j = 0; j < 10; j++ )
               a[i][j] = i * j;
   }


Additional reference words: 4.00 4.10
KBCategory: kbtool kbcode kbbuglist
KBSubcategory: CvwIss
Keywords : kb16bitonly


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.