Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner

Conditional breakpoint causes VS to crash

I have a problem with conditional breakpoints - if I place a breakpoint in the code and specify a condition that uses a logical variable, VS crashes once the breakpoint location is reached. If I remove the condition, everything is OK and VS does not crash.

Breakpoint is set in a global subroutine (not in any module), the logical variable is used from a module (let's call it "Settings"), so the subroutine contains the line "use Settings, only : applyCorrection". The breakpoint condition is "applyCorrection.eq..TRUE.".

Am I specifying the breakpoint condition incorrectly?

I use VS 2010 Professional SP1 and IPS XE 2016 Update 3 on Windows 7 Professional SP1. 

0 Kudos
7 Replies
Highlighted

Can you provide more details

Can you provide more details about the condition? What is the expression? Do you use "is true" or "has changed"?

Retired 12/31/2016
0 Kudos
Highlighted
Beginner

I am sorry, I forgot to be

I am sorry, I forgot to be more specific. The expression is mentioned in my original post, it is

applyCorrection.eq..TRUE.

where logical*4 :: applyCorrection is a module variable and "Is true" is used in the breakpoint condition.

0 Kudos
Highlighted
Black Belt

I don't know about the

I don't know about the innards of the VS expression evaluator, but in Fortran you should have used

    IF (applyCorrection) ...

instead of using the comparison operator .EQ., which should not be used to compare logical variables.

0 Kudos
Highlighted
Valued Contributor II

applyCorrection.eq..TRUE. !

applyCorrection.eq..TRUE. ! throws an error

applyCorrection.eqv..TRUE. !works ok

In an example I made

but whey not have the condition as just applyCorrection

0 Kudos
Highlighted

What I see is that if I use

What I see is that if I use .EQ. in the condition, the breakpoint isn't hit. If I use .EQV. it is. I can also just put the name of the variable as the condition and select "Is true". But I don't get a VS crash. This is in VS2010 with 16.0.3.

Retired 12/31/2016
0 Kudos
Highlighted
Valued Contributor II

additional: I note in your

additional: I note in your other thread you have VS2010, I tested in VS2013 and at run time that says the condition is invalid so maybe that is an improvement to VS2010  just crashing....

0 Kudos
Highlighted
Beginner

Thank you for your quick help

Thank you for your quick help how to make the conditional breakpoint using logical variable work. I will give it a try after updating XE 2016 to Update 4. :-)

0 Kudos