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:	<000401c426a8$99a90a50$3200000a@picard>
From:	"GregMo" <cygwin AT wyldryde DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<001901c4268b$24649e20$3200000a AT picard>
Subject:	TCL Signal Handling
Date:	Tue, 20 Apr 2004 03:25:03 -0400
MIME-Version:	1.0
X-IsSubscribed:	yes
Note-from-DJ:	This may be spam

Okay, I'm prepared to be chastised as I'm fubbling in the dark here, but
does anyone know much about signal handling in TCL?  From what I have
gathered on the subject, TCL doesn't inheritly have any handling functions
but one can obtain extentions to add these in.  Has anyone done this on
cygwin?

The really frustrating part here is that I'm working with a multi-threaded
TCL script that runs flawlessly on *nix, and all but works on cygwin.  When
it halts, it exits with 128 which indicates an unhandled signal from the OS.
Just a sheer guess, but I'm thinking it's because we're getting a signal
here from Windows that isn't present on *nix?  If so, is or isn't this
something that should be included in the porting of TCL?  Any suggestions
for a work-around to get things going?

TIA,
Greg



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.659 / Virus Database: 423 - Release Date: 4/15/2004


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

- Raw text -