QCW9112001: Conditional Breakpoints Cannot Always Be Set

ID Number: Q78853

1.00

WINDOWS

buglist1.00

Summary:

PROBLEM ID: QCW9112001

SYMPTOMS

When using Microsoft QuickC for Windows (QC/Win) version 1.0,

setting conditional breakpoints in a debugging session may not

work correctly.

A message box may be posted with a message such as

The breakpoint ?"a" cannot be set.

where ?"a" is the conditional breakpoint set.

CAUSE

The problem occurs only when the breakpoint is set when the

variable is out of scope.

RESOLUTION

Ensure the breakpoint is set when the variable is in scope. In the

example below, trace into the program and then set the breakpoint.

STATUS

Microsoft has confirmed this to be a problem in QC/Win version 1.0.

We are researching this problem and will post new information here

as it becomes available.

More Information:

To generate the problem:

1. Copy the code example into a new file while in the QC/Win

environment.

2. Select Options from the main menu and then choose Project. Set the

Program Type to QuickWin EXE and click the OK button.

3. Choose Build from the Project menu; this will completely build the

sample program.

4. Choose Breakpoints from the Debug menu and a dialog box will

appear.

5. Set Break: to "If Expr is True" and add "a" to the Expression:

box. The default length is 1 and this is the size of "a"; so just

choose the Add button after doing this.

6. Choose OK and then run the program by pressing F5.

At this point the above message box will appear and the breakpoint

will not be set. When OK is chosen in the message box, the program

will run to termination since no breakpoints were seen.

Sample Code

-----------

// compile options needed: none

void main(void)

{

char a;

a='a';

}

Additional reference words: 1.00