I have the same problem with InterSystems Caché running under Windows 7 under Fusion 8.5.3 running on my Mac. However, my friend down the hall with a similar configuration does not have the problem. The major difference is that I run Cygwin on my Windows system to give me Unix capabilities so I can run bash scripts on Windows. The lack of Ctrl-C pass through occurs in an InterSystems supplied Windows console application that provides terminal access to Caché. If I directly connect to a Caché job from a cmd.exe window I get the same behavior where the Ctrl-C is not passed through to the running application but instead cmd.exe sees the ctrl-C and terminates my applicaition.
The reason why I suspect Cygwin is involved is that if I run a Caché session from a Cygwin bash shell window then things are much worse. The Caché csession application is not getting Ctrl-C passed through so that bash kills the application if a ctrl-C is typed but now the of the graphic characters that I type seem not to be recognized. The prompt string is correctly printed in the Cygwin bash window but after that if I type a command line followed by a return then that command is just echoed back in the bash window but it is not executed by the Caché application.
Are any of the other people with this Ctrl-C problem using Cygwin on the Windows system?
