Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <99B82AA9708ED0119B55006097125A002DE8F5@ifk63.mach.uni-karlsruhe.de> From: Heribert Dahms To: "'Chris Faylor'" , "Fifer, Eric" Cc: "'Ray Easton'" , cygwin AT sourceware DOT cygnus DOT com Subject: RE: call_handler, interrupt_now and interruptible Date: Fri, 4 Feb 2000 22:45:14 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1457.3) Content-Type: text/plain Hi Chris, I guess this breaks now my code, which basically does a select() until a socket becomes readable, starts a loop preparing a timeout with alarm(60) for the following blocking fgets(), which is normally reset using alarm(0) after each line, but is supposed to be interrupted in case of a bad behaving client? Bye, Heribert (heribert_dahms AT icon-gmbh DOT de) > -----Original Message----- > From: Chris Faylor [SMTP:cgf AT cygnus DOT com] > Sent: Friday, February 04, 2000 00:26 > To: Fifer, Eric > Cc: 'Ray Easton'; cygwin AT sourceware DOT cygnus DOT com > Subject: Re: call_handler, interrupt_now and interruptible > > On Thu, Feb 03, 2000 at 06:38:43PM -0000, Fifer, Eric wrote: > > > >"Ray Easton" writes: > >>> Anyways, is this dangerous to do? > >> > >>If 'this' means interrupting a DLL while it is "paused on a system > >>call", yes, it is extermely dangerous and can leave the NT kernel in > a > >>corrupt state. (This has nothing to do with Cygwin -- this is > purely > >>an NT issue.) > > [Heribert] [snip] > > The answer to your question is that this *is* dangerous to do. It > allows > cygwin "system calls" to be interrupted. > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com