X-Spam-Check-By: sourceware.org Date: Mon, 23 Jan 2006 12:05:13 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: SIGALRM is ignored in generated code blocks (using mmap) - testcase included Message-ID: <20060123170513.GA30212@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <5.0.0.25.2.20060123114614.00c48ca8@pop3.demon.co.uk> <20060123124552.GO5636@implementation.labri.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060123124552.GO5636@implementation.labri.fr> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Jan 23, 2006 at 01:45:52PM +0100, Samuel Thibault wrote: >Lee Moore, le Mon 23 Jan 2006 12:05:17 +0000, a ?crit : >> I have an application which is creating generated code blocks in memory >> provided by mmap, once the application is running in the generated code >> blocks, it cannot be interrupted by a SIGALRM. > >Mmm, IIRC signals can't be delivered unless you call cygwin functions. If that is actually true, it's a bug. Cygwin should be able to interrupt user code. It doesn't try to interrupt... >Another problem can this this too: >int main(void) { > signal(SIGALRM,handler); > alarm(1); > Sleep(); >} ...a Windows function like Sleep. It should interrupt, e.g., a busy loop in user code, however. cgf -- 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/