Difference between revisions of "Ctrl C"
| Line 3: | Line 3: | ||
On Windows, the handling of SIGINT (aka Ctrl+C for a DOS prompt) is done in a different thread than the running thread. Which means that the current runtime cannot handle it properly without failing, since it throw the exception in the wrong thread. | On Windows, the handling of SIGINT (aka Ctrl+C for a DOS prompt) is done in a different thread than the running thread. Which means that the current runtime cannot handle it properly without failing, since it throw the exception in the wrong thread. | ||
| − | I've posted a question on the Microsoft newsgroups and here is the [http://groups.google.ie/group/microsoft.public.win32.programmer.kernel/browse_frm/thread/b0bdada7bae7ffa4/e4ea8cd55871b466?tvc=1&hl=en#e4ea8cd55871b466 thread]. The interesting part of | + | I've posted a question on the Microsoft newsgroups and here is the [http://groups.google.ie/group/microsoft.public.win32.programmer.kernel/browse_frm/thread/b0bdada7bae7ffa4/e4ea8cd55871b466?tvc=1&hl=en#e4ea8cd55871b466 thread]. The interesting part of my thread is a reference to [http://groups.google.ie/group/microsoft.public.win32.programmer.kernel/browse_frm/thread/608ad10204f76515/1e175f06dca6106f?hl=en#1e175f06dca6106f another discussion thread] where they propose a solution. |
This needs to be investigated. | This needs to be investigated. | ||
Revision as of 15:51, 6 June 2007
On Windows, the handling of SIGINT (aka Ctrl+C for a DOS prompt) is done in a different thread than the running thread. Which means that the current runtime cannot handle it properly without failing, since it throw the exception in the wrong thread.
I've posted a question on the Microsoft newsgroups and here is the thread. The interesting part of my thread is a reference to another discussion thread where they propose a solution.
This needs to be investigated.
