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

Problem to let debugger stop at the crash point

paramont
Beginner
‎04-04-2003 07:14 PM
635 Views
I tried use ISNAN. It compiled ok, but when I ran it, it crashed immediately, with the error message of:
First-chance exception in f2d.exe: 0xC0000005: Access Violation.
The thread 0x58C has exited with code -1073741667 (0xC000009D).
The program 'C:francf2dDebugf2d.exe' has exited with code -1073741667 (0xC000009D)
And the debugger can't stop at the point where my project crashed.

Could you please tell me about these messages?

Thanks.
0 Kudos

Link Copied

4 Replies
Steven_L_Intel1
Employee
‎04-05-2003 02:04 AM
635 Views
What version of Visual Fortran do you have? See my response in your NaN topic regarding access violation. The debugger should stop automatically...

Steve
0 Kudos
Copy link
paramont
Beginner
‎04-05-2003 04:07 AM
635 Views
I am using CVF 5.0A
0 Kudos
Copy link
Jugoslav_Dujic
Valued Contributor II
‎04-05-2003 08:37 AM
635 Views
1. Make sure to upgrade to 5.0D

2. You have to define environment variable FOR_IGNORE_EXCEPTIONS=TRUE*. On Win2k, it is in My Computer/Properties/Advanced/Environment variables. On Win9x, you should add it to Autoexec.bat

Jugoslav
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎04-05-2003 02:34 PM
635 Views
Another option in 5.0 is Debug..Exceptions and then change the action for Access Violation to "Stop Always". This isn't needed in 6.0 and later.

Steve
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.