- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using IVF 11.1.038 and have been getting the following error: "forrtl severe (8): internal consistency check failure, for_intro_fmt.c. line 2230". I get this error when I compiler using the release configuration. Everythings seems fine when I use the debug configuration. If I set /traceback and /check:pointer in release mode all seems to work well also. This is making finding a codingerror very differcult. My guess is there is something going on with memory but where do I start to look? Any suggestions would be appreciated.
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's indeed possible that memory is being corrupted and that any change in code generation or data layout can have an effect on this. You can try turning off optimization on selected source files until you find the one (hopefully) that, when compiled with optimization, causes the error. If the source has multiple procedures, split them out into separate files and repeat the process.
If you can't find it, let us look at it - submit it to Intel Premier Support or attach it here with enough to reproduce the problem.
If you can't find it, let us look at it - submit it to Intel Premier Support or attach it here with enough to reproduce the problem.
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
GO NAVY! (had to do that, my daughter is 05 USNA Grad!)
i am guessing it is related to something the Optimizer is doing.
In your Release setup, try turning off Optimization (it'll still run fast!) and that should get you up andrunning.
Project -> Properties->Fortran->Optimization->Disable (/Od)
i am guessing it is related to something the Optimizer is doing.
In your Release setup, try turning off Optimization (it'll still run fast!) and that should get you up andrunning.
Project ->
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's indeed possible that memory is being corrupted and that any change in code generation or data layout can have an effect on this. You can try turning off optimization on selected source files until you find the one (hopefully) that, when compiled with optimization, causes the error. If the source has multiple procedures, split them out into separate files and repeat the process.
If you can't find it, let us look at it - submit it to Intel Premier Support or attach it here with enough to reproduce the problem.
If you can't find it, let us look at it - submit it to Intel Premier Support or attach it here with enough to reproduce the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
It's indeed possible that memory is being corrupted and that any change in code generation or data layout can have an effect on this. You can try turning off optimization on selected source files until you find the one (hopefully) that, when compiled with optimization, causes the error. If the source has multiple procedures, split them out into separate files and repeat the process.
If you can't find it, let us look at it - submit it to Intel Premier Support or attach it here with enough to reproduce the problem.
If you can't find it, let us look at it - submit it to Intel Premier Support or attach it here with enough to reproduce the problem.
Thanks for the advice. I found the bug.
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