Re: Terminate Thread in DoInterruptible in Win32

[Sam S. <sd...@gn...>]

> * In message <249...@ic...>
> * On the subject of "Terminate Thread in DoInterruptible in Win32"
> * Sent on Sun, 17 Feb 2002 14:39:28 +1000
> * Honorable Arseny Slobodjuck <am...@ic...> writes:
>
>   Seems that problem in following: when some code is executed in
>   separate thread of some process, on NT or (I suspect) win2000 and
>   XP, the result of pressing Ctrl-=F3 may or may not be in (system-level)
>   terminating of this thread. On windows 95 ctrl-c-ed thread never
>   being terminated by system (or it happens 1 time of 1000 ?).
>=20=20=20
>   Seems that even Sleep(2000) don't help a fine thread to die.

okay - so why not just remove the sleep() call?

>   tt-quiet.dif is normal patch.

look good.
(un?:-)fortunately, I no longer have any access to an nt machine.
thus I cannot test your patch.
it appears to be simple enough though, so I will put it in relying on
your word. :-)

1. Does CLISP build with it?
2. Does it fix the problem (_without_ sleep()) - i.e., does C-c
   terminate (or abort one debug level) without the error message?
3. does 'cd test;make' work fine?

thanks!

--=20
Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux
Keep Jerusalem united! <http://www.onejerusalem.org/Petition.asp>
Read, think and remember! <http://www.iris.org.il> <http://www.memri.org/>
Whom computers would destroy, they must first drive mad.