This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/221] C++ throw terminates ucontext_t context, instead of returning via uc_link
- From: "a dot darovskikh at compassplus dot ru" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 18 Jun 2004 11:32:38 -0000
- Subject: [Bug libc/221] C++ throw terminates ucontext_t context, instead of returning via uc_link
- References: <20040616095113.221.a.darovskikh@compassplus.ru>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- 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.