- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm having a problem when debugging a console application using Intel Fortran Compiler 10.1.021 (IA-32) with Visual Studio .NET 2003.
Everything is written in fortran and compiles, builds and runs nicely. However, if I try debugging it, there is
Unhandled exception at : User breakpoint
which stops the debugger at a line like
open(unit=12,file=name,status='old',form='formatted')
where name is declared variable. Is it possible to debug the code with file I/O operations?
Thanks,
Grgur
I'm having a problem when debugging a console application using Intel Fortran Compiler 10.1.021 (IA-32) with Visual Studio .NET 2003.
Everything is written in fortran and compiles, builds and runs nicely. However, if I try debugging it, there is
Unhandled exception at : User breakpoint
which stops the debugger at a line like
open(unit=12,file=name,status='old',form='formatted')
where name is declared variable. Is it possible to debug the code with file I/O operations?
Thanks,
Grgur
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Look behind the Visual Studio window for a message box or the console window. There you will likely see an error about a reference to an uninitialized variable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Steve,
Thanks for such a fast reply and sorry for my shortsightedness. The variable was initialized, but the file was in the wrong folder so it couldn't be found.
Thanks,
Grgur
Thanks for such a fast reply and sorry for my shortsightedness. The variable was initialized, but the file was in the wrong folder so it couldn't be found.
Thanks,
Grgur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, right. I/O errors also trigger a "user breakpoint" with the message in the console window (or a message box.) Unfortunately, VS takes control and hides the window, so you may not notice it. A common problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's good practice to usethe ERR and IOSTAT arguments in open/close, read/write, and inquire to handle this sort of thing.
Gerry

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page