Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-Id: From: newsham AT lava DOT net (Tim Newsham) Subject: exceptions in cygwin.dll? To: cygwin-developers AT sourceware DOT cygnus DOT com Date: Fri, 19 Mar 1999 13:13:25 -1000 (HST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, How does cygwin handle the following case: - a signal handler is registered for SIGSEGV - a program makes a call into cygwin.dll - cygwin.dll blocks signal handler dispatch - a memory fault occurs - the exception handler notices that there is a handler, and doesn't terminate the program - the exception handler notices that signal handlers dispatch is temporarily disallowed, and returns I believe this is the series of events causing programs to occasionally loop forever in an unkillable state printout out ACCESS_VIOLATION messages, using an older DLL. After an exception has been "handled", the program returns excecution to the faulting code and it happens all over again... Is this a realistic diagnosis? Has this case been considered and dealt with in the current DLL? What can be done to prevent this from happening? I've been unable to think of a workaround for this case. Tim N.