This is the mail archive of the email@example.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
exceptions in cygwin.dll?
- To: firstname.lastname@example.org
- Subject: exceptions in cygwin.dll?
- From: email@example.com (Tim Newsham)
- Date: Fri, 19 Mar 1999 13:13:25 -1000 (HST)
- Delivered-To: firstname.lastname@example.org
- Delivered-To: mailing list email@example.com
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- Sender: email@example.com
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.