delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
Message-Id: | <199906161218.OAA17417@margaux.inria.fr> |
X-Authentication-Warning: | margaux.inria.fr: Host diaz AT localhost didn't use HELO protocol |
X-Mailer: | exmh version 1.6.4 10/10/95 |
To: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | exceptions... |
Mime-Version: | 1.0 |
Date: | Wed, 16 Jun 1999 14:18:57 +0200 |
From: | Daniel Diaz <Daniel DOT Diaz AT inria DOT fr> |
Hello, I'm porting GNU-Prolog under cygwin and I have some questions about exceptions in cygwin: How could I get the fault address inside a SIGSEGV handler ? What can I exactly do inside such a handler ? In particular I'd like to emit a message (printf) and to exit (exit(1)). After that very often win95 run into troubles ? Can I use win32 API exception routines like: SetUnhandledExceptionFilter(), GetExceptionInformation(), GetExceptionCode(),... ? Thank you. -- =============================================== Daniel Diaz University of Paris 1 INRIA Rocquencourt 75013 Paris 78153 Le Chesnay Cedex FRANCE FRANCE email: Daniel DOT Diaz AT inria DOT fr =============================================== -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |