We have an issue with one of our tools that uses the IDL-Java bridge. After using the tool, we find that using Ctrl-c no longer generates interrupts for the rest of the IDL session. (We're seeing this with IDL 8.4 on the command line on Linux and Mac machines.) After some experimenting, we've found that the following is enough to reproduce the behavior: (Start IDL) IDL> ^C % Interrupt encountered. IDL> obj = OBJ_NEW('IDLjavaObject$java_lang_thread', 'java.lang.Thread') IDL> ^C (Nothing happens) If we press Ctrl-c while a pure IDL procedure is running, it will continue to run and finish as though Ctrl-c was not pressed at all. If we press Ctrl-c before calling a Java method or while the method is running, we never get the IDL prompt back. Is there a way to make IDL respond to Ctrl-c after using the IDL-Java bridge?