On Wed, Jun 16, 2004 at 08:13:09AM +0300, Jani tiainen wrote:
>Christopher Faylor wrote:
>>On Tue, Jun 15, 2004 at 03:37:05PM +0300, Jani tiainen wrote:
>>
>>>Christopher Faylor wrote:
>>>
>>>>On Tue, Jun 15, 2004 at 09:58:16AM +0100, John Cooper wrote:
>>>>
>>>>>Is it a known limitation that "native" Windows programs cannot be
>>>>>suspended?
>>>>
>>>>Yes. Window programs do not understand cygwin signals.
>>>
>>>Thats true for cygwin part. Native programs still can be
>>>suspended/resumed but not by cygwin (or shell that is running and
>>>waiting finishing of active process).
>>
>>
>>It is true for any part that Windows programs do not understand cygwin
>>signals.
>>
>>There is no way to reliably suspend a Windows programs.
^^^^^^^^
>
>Yes there is ( piece of pseudo code):
>
>For Each Thread THREAD_Y in Process PROCESS_X
> Call_Win32API SuspendThread(THREAD_Y.Handle)
>Next
>
>NOTE: In Win2k and later you need THREAD_SUSPEND_RESUME rights for
>particular thread.
I do have a fair amount of experience in this area. SuspendThread
cannot be used to *reliably* suspend a native windows app. If you
suspend the program at the wrong time you get hangs and other unwanted
behavior.
--
Christopher Faylor spammer? -> [EMAIL PROTECTED]
Cygwin Co-Project Leader [EMAIL PROTECTED]
TimeSys, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
