Perhaps somebody can help me in diagnosing a IVF 9 run-time error. I get a clean compile and link. Then I get a run-time error just as I call a subroutine (I know this because I wrote to a file just before the call then the first executable line of the subroutine). All the subroutine arguments are declared and defined prior to the call. I'm not sure what else I can check. Perhaps I need to update IVF or add one or more patches? Maybe there are project settings and debugging techniques that can shed more light on the problem.
After navigating to the Intel Registration Center, I see "w_fc_p_10.1.013.exe" is available for download (not "w_fc_c_10.1.013.exe"); is that the one for me?
This mysterious error appears to be from due to a stack overflow. So how do I increase the stack size for my projectto an adequate size in the Visual Studio 2005 environment?
So do I need to iteratively adjust the stack size (the value in the setting, Linker > System > Stack Reserve Size) until this error goes away? I would have thought that this is the kind of detail a compiler is supposed to take care of.
The compiler has no idea how much stack space is needed. In general you can pick a high value (100000000 for instance) without harm.
If you used a newer version of the compiler there is the option /heap-arrays which causes temporary arrays to be allocated on the heap rather than the stack. This is a better solution for most applications in my opinion.
It's about time to close this thread. The solution was to increase the Stack Reserve Size to 5000000 (at least for my application). Perhaps I can still increase this value(or use Steve's suggestion of using the heap) . Once I did this (but not before) the regular debugging diagnostics showed me the line where the unhandled exception originated. So the moral of the story is: if you get a mysterious run-time error (see above for the verbatim error message) that resists attempts to locate the origin it may well be a stack overflow. Thanks Steve!
