X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Message-ID: <1328068369.5448.6.camel@YAAKOV04> Subject: Re: llvm/clang 3.0-1 silently ignores C++ exception handling From: "Yaakov (Cygwin/X)" To: cygwin AT cygwin DOT com Date: Tue, 31 Jan 2012 21:52:49 -0600 In-Reply-To: <4F2835F0.5050704@t-online.de> References: <4F2835F0 DOT 5050704 AT t-online DOT de> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Tue, 2012-01-31 at 19:41 +0100, Christian Franke wrote: > Clang++ 3.0-1 does not produce any exception handling code. Unwind > tables and code within catch(.) {...} blocks are not generated. Throw > always abort()s program. > > Is this as excepted? As best as I can tell, this is an upstream limitation. Please feel free to take it upstream. Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple