Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29280 Discussions

Unhandled exception at 0x000000014020f297 in Macro3d+CLAMS.exe: 0xC00000FD: Stack overflow.

Ralph_Nelson
Novice
1,272 Views
I have looked at Steve's post here (http://software.intel.com/en-us/forums/showpost.php?p=12902) and looks like I'm trying to access zero (if the 0xC00000FD in the error message says that). Complete relievent files are attached.

But basically the error occurs when cfs1 calls clamslib (at line 102)
call clamslib(to, itemp, ierr)
and the clamslib routine definition looks like
subroutine clamslib(tn, isolflag, ierr)


I checked arguements etc. as Steve suggests and even printed them out. All appeared OK so I tried a few things but ultimately just deleted the arguements all together. So that the cfs1 statement is just
call clamslib
and the clamslib routine definition looks like
subroutine clamslib

Location of error changes but still get a reference to 0xC00000FD.

Note: When I compile I have array checking, uninitialize variables and null pointers turned on and am running in the debug mode.

Suggestions? I'm stumped.

Thanks


0 Kudos
3 Replies
mecej4
Honored Contributor III
1,272 Views
Please post the include files needed to compile the program.
0 Kudos
SergeyKostrov
Valued Contributor II
1,272 Views
...looks like I'm trying to access zero (if the 0xC00000FD in the error message says that)...

[SergeyK]When an application tries to access memory at zero address an exception 0xC0000005
( Access Violation ) is always thrown. When exception0xC00000FD ( Stack Overflow ) happens
it means thata new guard page for the stack cannot be created. In another words, your
application used all memory allocated for the stack and anyattempt to use more
memory fails. This is why you have the Stack Overflow exception.

...
Location of error changes but still get a reference to 0xC00000FD.

[SergeyK] You could try to increase Stack Reserve and Commit values. As Steve recommends
these values shouldn't be to big. Try to do some tests and you could start with a value 16777216 (16MB ),
for example.

...

Note: When I compile I have array checking, uninitialize variables and null pointers turned on and am running in the debug mode.

Suggestions? I'm stumped.

Best regards,
Sergey
0 Kudos
Ralph_Nelson
Novice
1,272 Views
Worked great. Thanks Serg.

On to the next problem which I'm sure will turn up soon.
0 Kudos
Reply