Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28945 Discussions

Problem with QWIN graphics and debug

NotThatItMatters1
329 Views

My current ide is Microsoft VS2022 v. 17.9.2. I have some old working code which I can compile and launch, but the code bonks in debug mode when it reaches the line

 

LARGE_RESULT = GETWSIZEQQ(0_4, QWIN$SIZEMAX, WINFO)

 

All variables are declared as follows:

Module level:

USE IFQWIN, ONLY : QWINFO
TYPE (QWINFO) :: WINFO

Routine level:

USE IFQWIN, ONLY : GETWSIZEQQ
USE IFQWIN, ONLY : QWIN$SIZEMAX

 

INTEGER (KIND = 4) LARGE_RESULT

 

The complaint is forrtl: error(65): floating invalid. What?

0 Kudos
6 Replies
Steve_Lionel
Honored Contributor III
311 Views

We'll need to see a reproducer, as small as you can manage.

0 Kudos
NotThatItMatters
Beginner
217 Views

Steve Lionel:

Thanks for the prompt response. I am finding it difficult to create the reproducer. I strip down the code to bare bones, but then it does not bonk. I try adding things, but none seem to cause the grief.

The only noteworthy thing I can report is, when I look at the debugger on the line in question and add a watch for the symbol

QWIN$SIZEMAX

it says it is undefined. That is unexpected.

0 Kudos
Steve_Lionel
Honored Contributor III
204 Views

By default, debug symbols for PARAMETER constants are omitted. You can change this in the project property page Fortran > Debugging. However, I find that the symbols aren't there no matter what.

0 Kudos
NotThatItMatters
Beginner
197 Views

Steve Lionel:

Thanks for the quick response. I will continue working on the reproducer.

The other feature here is the code is apparently running "properly" in Release mode. Just ran through an array of unit tests without issue.

0 Kudos
JohnNichols
Valued Contributor III
190 Views

Although it is not a great solution, and as long as the code can be in the public view, zip up the whole lot and put it on the forum.  Some one can then try it. 

0 Kudos
NotThatItMatters
Beginner
155 Views

I have a reproducer. I believe it has something to do with the compile/build options I have. In Compatibility, I am using the options

Use PowerStation I/O Format

Use PowerStation List Directed I/O Spacing

Use Other PowerStation Run-time Behavior

I have attached a zipped version of the project/solution.

0 Kudos
Reply