Handling Intel Fortran Runtime Errors from Managed Code

Question

I am tasked with porting a legacy software, to a Managed Language.

A few of the hard-coded calculation models are extremely time consuming to port, without gaining anything in terms of features or performance from a full port.

We decided to make a C++/CLI wrapper instead.

i.e. something like this:

FortranLib.h:

#pragma comment(lib, "fortranlibrary.lib")

extern "C" {
    void SUBROUTINENAME(int * param1, int * param2, float * param3, int * returnCode);
}

using namespace System;

namespace FortranlibraryWrapper {
    public ref class FortranLib{
        public:
            enum class ReturnCodes : int{
               ok = 0,
               //... and so on and so forth
            }

            ReturnCodes SubRoutineName(int param1, int param2, float param3);
    }
}

FortranLib.cpp:

#include "stdafx.h"
#include "FortranLib.h"
namespace FortranlibraryWrapper {

    FortranLib::CalculationReturnCodes FortranLib::SubRoutineName(int param1, int param2, float param3)
    {
         int returnCode = -1;
         SUBROUTINENAME( &param1, &param2, &param3, &returnCode);
         return (ReturnCodes)returnCode;
    }
}

We have in the actual code tried to bound params 1-3 to avoid issues, but apparently we are not good enough, as we recently we saw this type of error come up, in a new test case:

Intel(r) Visual Fortran run-time error

forrtl: severe (408): fort: (3): Subscript #1 of the array ....

This is due to some calculation in the fortran code, that determines an array index. but the calculated index is outside the bounds of the array.

The problem is that the error comes as an error dialogue, and does not raise an exception. We have already tried this:

         int returnCode = -1;
         try{
             SUBROUTINENAME( &param1, &param2, &param3, &returnCode);
         }
         catch(...)
         {
             throw gcnew System::Exception("fortran runtime error??");
         }
         return (ReturnCodes)returnCode;

and found that it does not catch anything..

The new application is intended as a server based service, so I need to somehow capture this error, and log it, and ideally continue the service, and discard the job that caused the failure.

Does anyone know how to accomplish that?

I would prefer not editing the fortran code, and recompiling it, as I am a novice with that language.