This is the mail archive of the
mailing list for the cygwin project.
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
- Date: Wed, 4 Jan 2006 14:06:17 -0500
- Subject: Re: Signals
- References: <20060104184322.GB15395@trixie.casa.cgf.cx> <SERRANOvhi6naDmUQ8h00000200@SERRANO.CAM.ARTIMI.COM>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
On Wed, Jan 04, 2006 at 06:49:04PM -0000, Dave Korn wrote:
>Christopher Faylor wrote:
>> On Wed, Jan 04, 2006 at 01:35:52PM -0500, Christopher Faylor wrote:
>>> On Wed, Jan 04, 2006 at 11:25:27AM -0700, John Buttitto wrote:
>>>> I wrote some simeple test code in Java to trap signals. Seems to work
>>>> well, I then ported it to cygwin. The code listens for the SIGINT and
>>>> prints a message. When I hit Ctrl-C while it is running the proper
>>>> signal gets sent and traped.
>>>> I then go to a second shell/Window and do a ps on the process running
>>>> and try to send a kill -s SIGINT <pid>. In cygwin this does not work the
>>>> process dies with out traping the signal.
>>>> Was wondering if anyone else ran into this and what silly thing I am
>>>> doing that causes the issue?
>>> There was a problem with the setup.ini file on sourceware.org. It should
>>> be fixed now but it will take a while to propagate.
>> Sorry. Somehow I responded to the wrong message. How embarrassing.
>Heh, I thought you were just emphasising your point about how it's a
>bad idea to hijack arbitrary threads for posting!
Actually, I was reading in one window and responding in another. Quite a
feat. Seeing how these things usually go, it'll probably be the start of
a new trend for me.