topic debug assertion failed in Intel® Fortran Compiler

debug assertion failed

sunshine177 — Sun, 19 Sep 2010 17:56:28 GMT

Hi,

my code generated the following error messages.

Debug Assertion Failed!

program...

File:winsig.c

Line:419

Expression: ("Invalid signal or error",0)

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?

debug assertion failed

Xiaoping_D_Intel — Mon, 20 Sep 2010 08:58:20 GMT

The error message shows it is stack overflow error. Have you tried "-heap-arrays" as Steve Lionel told in post #66306?

debug assertion failed

sunshine177 — Mon, 20 Sep 2010 23:20:44 GMT

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?

debug assertion failed

Wendy_Doerner__Intel — Mon, 20 Sep 2010 23:44:11 GMT

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

debug assertion failed

sunshine177 — Tue, 21 Sep 2010 00:03:34 GMT

Could you show me how to write over the stack on my own? I don't have much knowledge about CS. sorry.

debug assertion failed

Xiaoping_D_Intel — Tue, 21 Sep 2010 02:10:12 GMT

"-heap-arrays" should be applied to each compilation command line used to make object file.

debug assertion failed

Xiaoping_D_Intel — Tue, 21 Sep 2010 02:13:43 GMT

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.