From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7532 invoked by alias); 18 Jun 2004 11:32:39 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 7522 invoked by alias); 18 Jun 2004 11:32:38 -0000 Date: Fri, 18 Jun 2004 11:32:00 -0000 Message-ID: <20040618113238.7521.qmail@sourceware.org> From: "a dot darovskikh at compassplus dot ru" To: glibc-bugs@sources.redhat.com In-Reply-To: <20040616095113.221.a.darovskikh@compassplus.ru> References: <20040616095113.221.a.darovskikh@compassplus.ru> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/221] C++ throw terminates ucontext_t context, instead of returning via uc_link X-Bugzilla-Reason: CC X-SW-Source: 2004-06/txt/msg00084.txt.bz2 List-Id: ------- Additional Comments From a dot darovskikh at compassplus dot ru 2004-06-18 11:32 ------- Subject: Re: C++ throw terminates ucontext_t context, instead of returning via uc_link On Friday 18 June 2004 17:18, jakub at redhat dot com wrote: > ------- Additional Comments From jakub at redhat dot com 2004-06-18 11:18 > ------- I don't think anything like this is required by any standards. Maybe it's not required, literally, but in the terms of a common sense, this is nice to be implemented. In Windows (CreateFiber, SwitchToFiber, ...) this works nicely. If there's an exit it is used. I don't understand, why return works as expected, but exception does not. uc_link is designed for this purpose, isn't it? Maybe exceptions aren't listed in standards because ucontext is thought as a C API? Then there should be some kind of documented workaround, isn't it? -- http://sources.redhat.com/bugzilla/show_bug.cgi?id=221 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.