This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Bug? attempt to suspend = kill process?
- From: Linda Walsh <cygwin at tlinx dot org>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Thu, 05 Mar 2015 10:49:15 -0800
- Subject: Re: Bug? attempt to suspend = kill process?
- Authentication-results: sourceware.org; auth=none
- References: <54F7C550 dot 2010609 at tlinx dot org> <54F8358C dot 7040507 at towo dot net>
Thomas Wolff wrote:
Could signal transfer possibly use Windows in a way that does not have
this effect? (Windows experts...)
------
---
Utils like 'processhacker' (on source forge), have a suspend funtion
that allows you to suspend and continue both processes and threads,
I noticed a 2nd copy of bash that gets created between the original
shell and the win process (to handle stdio pipes, perhaps?), so
should be possible...but the exact mechanism...
Didn't know it was common knowledge for all win-progs to behave
that way (at one point control-c usually didn't work either), but
I thought it might have something to do with the added tty-emulation
abilities that allow multiple tty's and such...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple