public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "a dot darovskikh at compassplus dot ru" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/221] New: C++ throw terminates ucontext_t context, instead of returning via uc_link
Date: Wed, 16 Jun 2004 09:51:00 -0000	[thread overview]
Message-ID: <20040616095113.221.a.darovskikh@compassplus.ru> (raw)

When an exception occurs in another execution thread 
created with makecontext(), it causes program to exit 
with SIGABRT, instead of being catched in the main thread. 
 
Returning from this function works OK. I use recent GCC (3.4.0), 
and, as far as I understand, the problem is somewhere inside 
_Unwind_RaiseException, which doesn't check if it's another context. 
 
The test case is included.

-- 
           Summary: C++ throw terminates ucontext_t context, instead of
                    returning via uc_link
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: a dot darovskikh at compassplus dot ru
                CC: glibc-bugs at sources dot redhat dot com
  GCC host triplet: i686-pc-linux-gnu


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.


             reply	other threads:[~2004-06-16  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16  9:51 a dot darovskikh at compassplus dot ru [this message]
2004-06-16  9:54 ` [Bug libc/221] " a dot darovskikh at compassplus dot ru
2004-06-18  4:56 ` a dot darovskikh at compassplus dot ru
2004-06-18 11:18 ` jakub at redhat dot com
2004-06-18 11:32 ` a dot darovskikh at compassplus dot ru
2004-08-10  2:26 ` drepper at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040616095113.221.a.darovskikh@compassplus.ru \
    --to=sourceware-bugzilla@sources.redhat.com \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).