Home > Archive > Tcl > February 2005 > Re: How to detect that an external process stopped because of a crash (on Windows)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: How to detect that an external process stopped because of a crash (on Windows)
|
|
| Helmut Giese 2005-02-22, 4:02 pm |
| On Mon, 21 Feb 2005 10:30:56 +0100, Arjen Markus
<arjen.markus@wldelft.nl> wrote:
>Hello,
>
>I would like to ask you about a rather nasty property of Windows:
>Sometimes when a program does something it should not, Windows
>helpfully puts up a message box stating that fact and then
>the process waits for confirmation by the user.
Hi Arjen,
if the processes you start are under your control (that is, you have
the sources), you can modify them to not pop up this message. Turn to
your helpful Tcl sources :)
The win-pipe tests or rahter some specially crafted parts of tcltest
perform this magic via a Windows function call.
HTH
Helmut Giese
| |
| Helmut Giese 2005-02-22, 4:02 pm |
| On Tue, 22 Feb 2005 11:46:59 GMT, hgiese@ratiosoft.com (Helmut Giese)
wrote:
>Hi Arjen,
>if the processes you start are under your control (that is, you have
>the sources), you can modify them to not pop up this message. Turn to
>your helpful Tcl sources :)
>The win-pipe tests or rahter some specially crafted parts of tcltest
>perform this magic via a Windows function call.
Ok, just had a look myself. From tclWinTest.c
---
/*
* Make sure the GPF dialog doesn't popup.
*/
SetErrorMode(SEM_FAILCRITICALERRORS | SEM_NOGPFAULTERRORBOX);
---
HTH
Helmut Giese
|
|
|
|
|