Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Can't set conditon and data breakpoints

jq2000
Beginner
‎07-29-2003 02:55 AM
637 Views
When I set condition breakpoint or data breakpoint (memory address debugging), the breakpoints were disabled with warning message and stop at the begining of a program. Then the debugger refused to let me to reset the breakpoints. If I start running the debugger first, then set the breakpoints, Dev Studio did not permit me to set them. This problem does not alway happen. What I missed?
0 Kudos

Link Copied

2 Replies
Jugoslav_Dujic
Valued Contributor II
‎07-29-2003 09:58 AM
637 Views
Unfortunately, I don't think you missed anything.

Conditional breakpoints in VS seem to have a logic of its own, which usually doesn't match yours or mine :-(. I observe the same behaviour. For what it's worth, setting a normal breakpoint AFTER program start, then converting it to conditional one works most of the time, but the next time you restart the debugger you have to go all the way through again.

AFAIK there's little Intel guys can do here -- it's in the Microsoft part.

Jugoslav
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎07-29-2003 02:05 PM
637 Views
To add to what Jugoslav said, the MS debugger requires that, for a conditional breakpoint to be enabled, the expression must be capable of being evaluated at the point of enabling. That means that if you have a subroutine local variable in the expression, the debugger will refuse to enable it unless that subroutine is in scope (is executing). Furthermore, if it goes out of scope, the breakpoint is disabled.

Steve
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.