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.
29284 Discussions

Difficuty debugging a graphics program

WSinc
New Contributor I
524 Views

I have this simple little graphics program that plots a cubic function. It runs fine, but the trouble comes when I insert breakpoints.

It stops at the breakpoint and shows me the code window, but then I have no way of viewing the graphics window. I click on the minimized window, but nothing happens.

I have the same problem even when I use the "standard graphics project" but there the preoblem is even worse, because the graphics window disappears completely. The only way to get it back is to continue running the program AFTER the breakpoint.

I though there was supposed to be a way to switch between the code and output windows when the program was stopped at a breakpoint. I would like to see what it has printed or plotted up to that point at least.

Any clues? See attached code file.

0 Kudos
3 Replies
Steven_L_Intel1
Employee
524 Views
The problem is that when you interrupt your program at a breakpoint, EVERYTHING in the program stops, including message processing and, critically, window repainting. Clicking on the graphic window does nothing because the code that normally runs to repaint the window isn't executing. I don't know of a way around that - perhaps others do.
0 Kudos
jimdempseyatthecove
Honored Contributor III
524 Views

Reduce the size of the IDE (Debugger) window and of the graphics window so both are in viewor use dual monitors with one open to the IDE/Debugger and the other open to your application. I couldn't get along without at least 2 monitors on my development system.

Jim Dempsey

0 Kudos
onkelhotte
New Contributor II
524 Views

I know that problem... There are only two ways:

- Reduce the size of the IDE window so you can see the areabefore the IDE stops
- Use 2 displays

I use 2 displays and it is much easier to debug now.

Markus

0 Kudos
Reply