- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is an example case for a catastrophic error. I was able to reproduce the error. I did find out that the error occurs in the first 3 subroutines (constructors), at least the error does not occur when these routines are deleted.
This is the error upon compiling:
: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
compilation aborted for CatastrophicClass.f90 (code 3)
This is the error upon compiling:
: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
compilation aborted for CatastrophicClass.f90 (code 3)
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. We'll investigate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
Thanks. We'll investigate.
These are the options I am using:
ifort -O0 -g -fp-stack-check -traceback -gen-interface -warn interface
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I apologize for the delay in getting back to you on this one.
The internal compiler error is triggered by a coding error in the source. In routine NewCatastrophic2 you have:
call this%ImplicitTimeFlag(.false.)
this is supposed to be:
call this%SetImplicitTimeFlag(.false.)
The compiler should have given you an appropriate error message for this. I'll report that to the developers. Issue ID is DPD200149063
The internal compiler error is triggered by a coding error in the source. In routine NewCatastrophic2 you have:
call this%ImplicitTimeFlag(.false.)
this is supposed to be:
call this%SetImplicitTimeFlag(.false.)
The compiler should have given you an appropriate error message for this. I'll report that to the developers. Issue ID is DPD200149063
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
I apologize for the delay in getting back to you on this one.
The internal compiler error is triggered by a coding error in the source. In routine NewCatastrophic2 you have:
call this%ImplicitTimeFlag(.false.)
this is supposed to be:
call this%SetImplicitTimeFlag(.false.)
The compiler should have given you an appropriate error message for this. I'll report that to the developers.
The internal compiler error is triggered by a coding error in the source. In routine NewCatastrophic2 you have:
call this%ImplicitTimeFlag(.false.)
this is supposed to be:
call this%SetImplicitTimeFlag(.false.)
The compiler should have given you an appropriate error message for this. I'll report that to the developers.
Thanks Steve, not for the first time, my crappy programming has saved the day :)
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