From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31117 invoked by alias); 18 Jun 2004 11:18:06 -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 30971 invoked by uid 48); 18 Jun 2004 11:18:04 -0000 Date: Fri, 18 Jun 2004 11:18:00 -0000 Message-ID: <20040618111804.30970.qmail@sourceware.org> From: "jakub at redhat dot com" 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/msg00083.txt.bz2 List-Id: ------- 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. For each target, one would have to describe the makecontext helper behaviour in terms of DWARF2/3 unwind info. Say on i386, the helper increases stack pointer by 4 * %ebx (easy), reads link pointer from the stack, then needs conditionally go to an area without unwind info (exit case) or simulate the effect of setcontext call. -- 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.