public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjmunroe at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/2377] New: Deadlock between dlclose and c++ exception/unwind
Date: Tue, 21 Feb 2006 16:52:00 -0000	[thread overview]
Message-ID: <20060221165241.2377.sjmunroe@us.ibm.com> (raw)

In this case an application is calling a library via dlopen/dlsym/dlclose. This
library created a service thread that it needs to terminate when dlclose is
called. But if the service thread takes an exception after the call to dlclose
and the libraries call to pthread_join then the service thread will hang in the
unwind code and the join will never complete.

-- 
           Summary: Deadlock between dlclose and c++ exception/unwind
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: critical
          Priority: P1
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: sjmunroe at us dot ibm dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: powerpc-linux
  GCC host triplet: powerpc64-linux
GCC target triplet: powerpc-linux


http://sourceware.org/bugzilla/show_bug.cgi?id=2377

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2006-02-21 16:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 16:52 sjmunroe at us dot ibm dot com [this message]
2006-02-21 16:55 ` [Bug libc/2377] " sjmunroe at us dot ibm dot com
2006-02-21 17:00 ` sjmunroe at us dot ibm dot com
2006-02-21 17:02 ` sjmunroe at us dot ibm dot com
2006-02-21 17:11 ` sjmunroe at us dot ibm dot com
2006-03-20 22:30 ` rsa at us dot ibm dot com
2006-03-21 20:36 ` rsa at us dot ibm dot com
2006-05-02 22:02 ` drepper at redhat dot com
2010-09-02 15:52 ` schwab at linux-m68k dot org

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=20060221165241.2377.sjmunroe@us.ibm.com \
    --to=sourceware-bugzilla@sourceware.org \
    --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).