Setting a conditional breakpoint 101

[TommyCee]

Hello all.  At long last, I have found it necessary to use one of ComposerXE's features that's supposed to let you set a breakpoint and run until some variable reaches a set value.  In this case, the variable is an integer.  Ideally, I'd like to run to a breakpoint until a variable in that scoping unit reaches some value, and then pause, allowing me to take over and then run debug on my own (e.g., using F5s or F10s to step through the code).  Is this a tall order?

Unfortunately, I don't see anything relating to "conditional breakpoints" in the Debug dropdown menu, and after searching this forum I don' really see any basic discussion on this functionality.

FWIW, I'm using VS2010 and have XE 2013.

Any suggestions?

[TommyCee]

Not bad, Steve, except the section Adding Conditions to File Breakpoints needs to be rewritten.  I'd be glad to do it, and send you a strawman.  How it should be rewritten, and what needs to be added, is clear from this thread.  As it is, it leaves too much to the imagination.

[Steven_L_Intel1]

Sure, send me your suggestions and I'll pass them on.

[FortranFan]

Steve Lionel (Intel) wrote:

You mean like this?

Thanks Steve.  I was looking in the wrong place:

• It might be helpful to have a link in the Getting Started -> Using Microsoft* Visual Studio* (Windows* OS) section to Compilation -> Debugging since it is not exactly easy to search within Help.  I wish one could restrict one's search and navigation to specific content, but that's a separate discussion.
• Also, as TommyCee pointed, the existing information on breakpoints appears thin on content and it leaves out the most critical information i.e., the syntax of breakpoint conditions.  So whatever your writers can do to improve content (using input from users such as TommyCee) will be valuable indeed.