I have a Visual Studio 2010 C dll that has a Intel Visual Fortran Composer XE 2011 static library that is linked to the C dll. This dll is loaded from a third party tool that uses Ctrl + C to interupt its iterpreter to lauch its debugger. However, the Ctrl + C is intercepted by the FORTRAN runtime and gives a forrtl: error (200): program aborting due to control-C event. According to the documentation, a dll should not have the default fortran runtime signal handling. Does anyone know if there are some compiler settings that can be set on the static library to prevent it from causing the runtime signal handling to intercept the control-C.
For more complete information about compiler optimizations, see our Optimization Notice.