topic Geoff, in Intel® Fortran Compiler

intel fortran DLL is klobbering my SIGINT handler!

Groos__Geoff — Fri, 17 Apr 2015 05:30:37 GMT

Hey guys,

I'm doing an integration piece between a Java front-end and a very mathy chunk of fortran we've written. We've got it being loaded and executed properly.

The one annoying thing is that I'm using the JVM to subscribe to SIGINT, so I can do some persistence-ee things if the user hits Ctrl + C on one of our command line tools. This works well, except for that if I load the fortran dll after the signal handler was registered with the JVM, the fortran DLL appears to over-write the signal handler I put in with its own.

Fortran's default SIGINT handler prints out this:

error (200): program aborting due to control-C event
Image              PC        Routine            Line        Source
SOGOV1.dll         6B0B69C8  Unknown               Unknown  Unknown
KERNELBASE.dll     772123C4  Unknown               Unknown  Unknown
KERNEL32.DLL       74E07C04  Unknown               Unknown  Unknown
ntdll.dll          775DB54F  Unknown               Unknown  Unknown
ntdll.dll          775DB51A  Unknown               Unknown  Unknown

Whereas mine is a little more subtle, and I've got it working so long as I use stub code and avoid loading the fortran code (SOGOV1.dll).

Thanks for any help!

-Geoff

Actually, it's the Console

Steven_L_Intel1 — Fri, 17 Apr 2015 15:36:35 GMT

Actually, it's the Console Control Event Handler that is doing this. In version 16, currently in beta, we have introduced a new environment variable FOR_DISABLE_CONSOLE_CTRL_HANDLER which, if you set it to 1 before running the program, will prevent the run-time library (RTL) from establishing this handler. Feel free to download the beta and try this.

The RTL does check to see if you have a SIGINT handler and should avoid overriding it if there is one, but perhaps this test is not working for your environment. It can't check for use of SetConsoleCtrlEventHandler, though, which is why we created this new environment variable.

Quote:Steve Lionel (Intel)

Groos__Geoff — Thu, 23 Apr 2015 21:59:57 GMT

Steve Lionel (Intel) wrote:

Actually, it's the Console Control Event Handler that is doing this. In version 16, currently in beta, we have introduced a new environment variable FOR_DISABLE_CONSOLE_CTRL_HANDLER which, if you set it to 1 before running the program, will prevent the run-time library (RTL) from establishing this handler. Feel free to download the beta and try this.

The RTL does check to see if you have a SIGINT handler and should avoid overriding it if there is one, but perhaps this test is not working for your environment. It can't check for use of SetConsoleCtrlEventHandler, though, which is why we created this new environment variable.

Thanks Dr Fortran!

I must admit I've had much more success asking technical questions on this board than I have technical ones about java on stack overflow.

I suppose this question is better off aimed at the Intel sales support, but we purchased our compiler license about 8 months ago now and I'm wondering: will we be able to upgrade to version 16 without additional cost? Also, are you confident enough in the current beta to suggest that we go to production with it if we cant find any problems? I would really like to get the ability to hit Ctrl + C to our customers soon, and this is the only thing blocking that.

Cheers,

-Geoff

Geoff,

Steven_L_Intel1 — Thu, 23 Apr 2015 23:30:17 GMT

Geoff,

Assuming the license I found for your company is correct - it's the only one for the Fortran Windows product that is still valid - then yes, you would be able to install and use version 16 when it first releases, and maybe even the first update. I see a support end date of November 28, 2015.

Version 16 beta is pretty good, but you can keep multiple versions around and select which one you want in Visual Studio. However, you must not "go to production" using a beta compiler!