From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1424 invoked by alias); 24 Nov 2004 03:20:33 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 1408 invoked from network); 24 Nov 2004 03:20:29 -0000 Received: from unknown (HELO mail.aaronwl.com) (68.228.0.128) by sourceware.org with SMTP; 24 Nov 2004 03:20:29 -0000 Received: from [70.182.14.214] (cdm-70-182-14-214.laft.cox-internet.com [70.182.14.214]) by mail.aaronwl.com (8.12.11/8.12.11) with ESMTP id iAO3KRA3022017; Wed, 24 Nov 2004 03:20:31 GMT Message-ID: <41A3FE7A.60005@aaronwl.com> Date: Wed, 24 Nov 2004 06:34:00 -0000 From: "Aaron W. LaFramboise" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: Danny Smith CC: gcc@gcc.gnu.org, Cygwin , mingw-dvlpr Subject: Re: stdcall lib functions with exception throwing callbacks vs Dwarf2 EH References: <001701c4d1ab$949322e0$0a6d65da@DANNY> In-Reply-To: <001701c4d1ab$949322e0$0a6d65da@DANNY> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-11/txt/msg00876.txt.bz2 Danny Smith wrote: > If a C library function that takes a callback arg is compiled > using stdcall convention, C++ exception thrown by the callback > result in abort. Just to speculate while not asking anyone to implement anything, would there be any value in implementing special behavior when throwing through non-dwarf2 code, such as checking for an SEH handler on the stack, or use the MSVC unwinding routines (which MinGW has access to, I beleive)? 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? Aaron W. LaFramboise