Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <6.0.1.1.2.20040218100902.02b562d8@pop.sonic.net>
X-Sender: rschulz AT pop DOT sonic DOT net
Date: Wed, 18 Feb 2004 10:29:16 -0800
To: cygwin AT cygwin DOT com
From: Randall R Schulz <rschulz AT sonic DOT net>
Subject: Re: Java Thread Dump in Bash
In-Reply-To: <4033A4BD.4050403@decodon.com>
References: <4031FE0B DOT 3060909 AT decodon DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 2 DOT 20040217072433 DOT 02ae6300 AT pop DOT sonic DOT net> <40327505 DOT 10005 AT decodon DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 2 DOT 20040217155517 DOT 03b5f0a8 AT pop DOT sonic DOT net> <4033A4BD DOT 4050403 AT decodon DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-IsSubscribed: yes

Frank-Michael,

I hesitate to continue this on the Cygwin list, but I will, for now.


At 09:45 2004-02-18, Frank-Michael Moser wrote:
>Randall, does your Java application die after pressing Ctrl-Break or not?

It appears it terminates. As you've had me trying this much more than I 
ever have in the past, I've found that the behavior is not really very 
uniform or predictable.

When the program's standard input and output are not redirected, I see 
the thread dump and the program dies--usually, but not quite always. 
Sometimes the program just terminates. I had interpeted the termination 
as an indication of an end-of-file having been generated, but that may 
have been incorrect.

When I run the program with standard input, output and error redirected 
to files and type CTRL-BREAK, the program terminates but the thread 
dump is nowhere to be seen in the file that received standard output, 
the file that received standard error nor the console / tty.


I could hypothesize that the recent changes in Cygwin signal handling 
might have something to do with this. However, I know nothing of the 
details of this change, just that a change was mentioned in the Cygwin 
release notes. So this is really just blind speculation, especially 
since I really don't have much of a basis for comparison (in a 
before-and-after sense).

Randall Schulz 


--
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/