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

Q re debugger window size

William_S_1
Beginner
225 Views

I have had trouble trying to readjust the size of the OUTPUT window

when I hit a break point. Very often, I want to scroll backwards, or see the 120 character lines

that a program might produce.

Is there a way to get the FULL window size and scroll history before hitting a break point?

You cannot do it AT the break point because the window disappears.

0 Kudos
3 Replies
mecej4
Honored Contributor III
225 Views

It is not clear whether you mean the VS Output Window, or the console window that the Fortran runtime opens for sending program output generated by statements such as WRITE(*,..). You probably mean the latter; if so, let the program run far enough to cause that window to be opened, right-click on the button at the top left corner of the window, and left-click on Properties. Set the width and height of the window, the size of the scroll buffer, etc.

If you want to have your settings persist across debugging runs, do so by using the Defaults menu item instead of the Properties menu item in the CMD.EXE window that your program creates, as described above.

0 Kudos
Steven_L_Intel1
Employee
225 Views

You're still doing a QuickWin application, right? You can't do ANYTHING to that window at a breakpoint - it isn't a regular console window but a bitmap window that requires the program be running so that the Windows "messages" for the window can be handled.

As an alternative, you can open a new "regular" console window and write to that. To do that, you'd have to call the Windows API routine AllocConsole:

use kernel32
...
iret = AllocConsole()

and then open unit 6 with FILE="CON" and write to unit 6. Then you'll have a separate console window you can scroll even when the program is stopped.
 

0 Kudos
andrew_4619
Honored Contributor II
225 Views
0 Kudos
Reply