public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cmetcalf at tilera dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug ports/15759] New: tile: C++11 destructors aren't working right
Date: Fri, 19 Jul 2013 18:42:00 -0000	[thread overview]
Message-ID: <bug-15759-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15759
           Summary: tile: C++11 destructors aren't working right
           Product: glibc
           Version: 2.18
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ports
          Assignee: unassigned at sourceware dot org
          Reporter: cmetcalf at tilera dot com
                CC: carlos at redhat dot com, roland at gnu dot org

The stdlib/tst-tls-atexit test fails with:

DSO not unloaded yet:
aaab580000-aaab590000 r-xp 00000000 08:03 3572837                       
/scratch/cmetcalf/glibc/64/stdlib/tst-tls-atexit-lib.so

The model is that there is supposed to be reference counting that causes the
DSO to get unloaded late, after the "official" call to dlclose() but also after
any thread destructors have run.

This code seems largely platform-independent, so it's strange that it fails for
tile.  It does work on x86_64.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-07-19 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19 18:42 cmetcalf at tilera dot com [this message]
2013-07-21 10:41 ` [Bug ports/15759] " siddhesh at redhat dot com
2013-07-22 16:01 ` cmetcalf at tilera dot com
2014-06-13 13:23 ` fweimer 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=bug-15759-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).