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 have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.

debug assertion failed

sunshine177
Beginner
1,298 Views
Hi,
my code generated the following error messages.
1.
Debug Assertion Failed!
program...
File:winsig.c
Line:419
Expression: ("Invalid signal or error",0)
2.
forrtl: severe <170>: Program Exception - stack overflow
Someone in this forum asked the same question ->http://software.intel.com/en-us/forums/showthread.php?t=66306
I guessed this is a problem of stack size, so I increased the Stack Reserve Size(100MB), stack commit size(100MB),heap reserve size(100MB),heap commit size(100MB), but it's not still working.
My laptop is 32-bit. I am using Intel Visual Fortran v11.1 and Visual Studio 2005.
I cannot run the code in 32-bit computer?
Anyone can help me with this?
0 Kudos
6 Replies
Xiaoping_D_Intel
Employee
1,298 Views
The error message shows it is stack overflow error. Have you tried "-heap-arrays" as Steve Lionel told in post #66306?
0 Kudos
sunshine177
Beginner
1,298 Views
I made object files and modules and then I typed the following
ifort [object files] -o main -heap-arrays -I"[library path]" [library files]
But the result is the same
->severe <170> : program exception - stack overflow
Anyone can figure this out?
0 Kudos
Wendy_Doerner__Intel
Valued Contributor I
1,298 Views
You can also write over the stack on your own. One way to check for coding errors is to add /check to the compiler to add runtime checks.

------

Wendy

Attaching or including files in a post

0 Kudos
sunshine177
Beginner
1,298 Views
Could you show me how to write over the stack on my own? I don't have much knowledge about CS. sorry.
0 Kudos
Xiaoping_D_Intel
Employee
1,298 Views
"-heap-arrays" should be applied to each compilation command line used to make object file.
0 Kudos
Xiaoping_D_Intel
Employee
1,298 Views
I think Wendy means writing over the stack by yourcode may also be a possible reason for the failure. To check such case you can add "-C" option (Here 'C' is uppercase) to your compilation command lines to enable runtime check.
0 Kudos
Reply