From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA02076; Thu, 7 Oct 2004 17:17:19 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA01177 for ; Thu, 7 Oct 2004 17:17:18 +0200 (MET DST) From: mattwb@comcast.net Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id i97FHHkQ023030 for ; Thu, 7 Oct 2004 17:17:17 +0200 Received: from 204.127.197.114 ([204.127.197.114]) by comcast.net (rwcrmhc13) with SMTP id <200410071517160150039eu4e>; Thu, 7 Oct 2004 15:17:16 +0000 Received: from [216.127.133.66] by 204.127.197.114; Thu, 07 Oct 2004 15:17:15 +0000 To: caml-list@inria.fr Subject: [Caml-list] Sys.sigint is blocked with cygwin threads Date: Thu, 07 Oct 2004 15:17:15 +0000 Message-Id: <100720041517.25930.41655DFA0005346A0000654A22007503300D999B9B0E03@comcast.net> X-Mailer: AT&T Message Center Version 1 (Sep 14 2004) X-Authenticated-Sender: bWF0dHdiQGNvbWNhc3QubmV0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="NextPart_Webmail_9m3u9jl4l_25930_1097162235_0" X-Miltered: at concorde with ID 41655DFD.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; mattwb:01 comcast:99 cygwin:01 threads:01 cygwin:01 threads:01 unblock:01 unblock:01 blocking:01 blocking:01 compile:02 compile:02 native:02 native:02 o'caml:02 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk --NextPart_Webmail_9m3u9jl4l_25930_1097162235_0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Is there a good reason that Sys.sigint is blocked when I compile a native application under Cygwin using threads? Is O'Caml doing the blocking or Cygwin? I would like to develop a service using cygrunsrv to run it, but that requires my application to take a signal when killed. Is it safe to unblock any signals when using threads under Cygwin? If so, which one's. --NextPart_Webmail_9m3u9jl4l_25930_1097162235_0 Content-Type: text/html Content-Transfer-Encoding: 8bit

Is there a good reason that Sys.sigint is blocked when I compile a native

application under Cygwin using threads? Is O'Caml doing the blocking or

Cygwin? I would like to develop a service using cygrunsrv to run it, but that

requires my application to take a signal when killed. Is it safe to unblock any

signals when using threads under Cygwin? If so, which one's.

--NextPart_Webmail_9m3u9jl4l_25930_1097162235_0-- ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners