Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Wed, 24 Nov 2004 00:36:23 -0500 From: Christopher Faylor To: Cygwin , gcc@gcc.gnu.org, mingw-dvlpr@lists.sourceforge.net Subject: Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH Message-ID: <20041124053623.GB13336@trixie.casa.cgf.cx> Mail-Followup-To: Cygwin , gcc@gcc.gnu.org, mingw-dvlpr@lists.sourceforge.net References: <001701c4d1ab$949322e0$0a6d65da@DANNY> <41A3FE7A.60005@aaronwl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A3FE7A.60005@aaronwl.com> User-Agent: Mutt/1.4.1i On Tue, Nov 23, 2004 at 09:22:34PM -0600, Aaron W. LaFramboise wrote: >Do any Windows system routines have any function local cleanup that >they'd need to do registered with SEH, or are they OK with suddenly >being zapped out of existance at user code call points? If cygwin's signal handling code is any indication, Windows system routines will become very unhappy if you just zap the PC away somewhere down (up?) the stack. On Windows 9x you'll eventually cause a system crash, in fact. 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/