- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I'm debugging a complex fortran code (MPI) thats giving the errors:
forrtl: severe (151): allocatable array is already allocated
I'm having a hard time debugging this: this is a code with built-in traceback analysis which makes working
with debuggers a pain - I can't get debugging working using ddt, and am trying to debug via core dumping.
Despite "ulimit -c unlimited' , I get no core dumps. I get core dumps for other SIGABRT situations, but can't
trigger one here. Is there a special environment variable I need?
Regards
Alastair
forrtl: severe (151): allocatable array is already allocated
I'm having a hard time debugging this: this is a code with built-in traceback analysis which makes working
with debuggers a pain - I can't get debugging working using ddt, and am trying to debug via core dumping.
Despite "ulimit -c unlimited' , I get no core dumps. I get core dumps for other SIGABRT situations, but can't
trigger one here. Is there a special environment variable I need?
Regards
Alastair
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can try setting the ifort specific run-time environment variable decfort_dump_flag to a value of Y, or y, or even 1 seems to work. This is a documented environment variable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Kevin Davis (Intel)
You can try setting the ifort specific run-time environment variable decfort_dump_flag to a value of Y, or y, or even 1 seems to work. This is a documented environment variable.
I was using this in Uppercase instead of lowercase. I'd forgotten env. variables are case-sensitive.
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