public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/12307] accessing thread local storage blocks forever when using dlopen
Date: Tue, 15 Oct 2013 06:15:00 -0000	[thread overview]
Message-ID: <bug-12307-131-Jo16m8zaIi@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12307-131@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Ondrej Bilka <neleai at seznam dot cz> ---
On Mon, Oct 14, 2013 at 11:09:34PM +0000, bugdal at aerifal dot cx wrote:
> --- Comment #3 from Rich Felker <bugdal at aerifal dot cx> ---
> Indeed, regardless of whether it's "stupid", as far as I know there's no formal
> reason it's invalid to create threads from a constructor and the bug is valid.
> 
And will you write a patch?

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


  parent reply	other threads:[~2013-10-15  6:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 17:13 [Bug libc/12307] New: " maxim.yegorushkin at gmail dot com
2011-08-24 10:36 ` [Bug libc/12307] " andrewjcg at gmail dot com
2012-02-21  2:16 ` [Bug ld.so|libdl/12307] " jsm28 at gcc dot gnu.org
2012-12-19 10:51 ` [Bug dynamic-link/12307] " schwab@linux-m68k.org
2013-10-13  8:58 ` neleai at seznam dot cz
2013-10-13 11:42 ` maxim.yegorushkin at gmail dot com
2013-10-14 23:09 ` bugdal at aerifal dot cx
2013-10-15  6:15   ` Ondřej Bílka
2013-10-15  6:15 ` neleai at seznam dot cz [this message]
2013-10-15  8:59 ` maxim.yegorushkin at gmail dot com
2014-06-30  6:22 ` 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-12307-131-Jo16m8zaIi@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).