public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libmudflap/44661] Link order (?) might cause threaded libmudflap to assert
Date: Wed, 21 Jul 2010 23:53:00 -0000	[thread overview]
Message-ID: <20100721235305.13037.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44661-19357@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from pinskia at gcc dot gnu dot org  2010-07-21 23:53 -------
I think libmudflapth does have a dependency on libpthread which is causing this
issue.  I think libmudflapth have a weak check in it too.

                 w pthread_join


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2010-07-21 23:53:05
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44661


  parent reply	other threads:[~2010-07-21 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25  5:08 [Bug libmudflap/44661] New: " davi dot arnaut at sun dot com
2010-06-28  0:48 ` [Bug libmudflap/44661] " pinskia at gcc dot gnu dot org
2010-07-21 23:53 ` pinskia at gcc dot gnu dot org [this message]
2010-07-22  7:53 ` jakub at gcc dot gnu dot org
2010-07-22 10:54 ` davi dot arnaut at sun dot com
     [not found] <bug-44661-4@http.gcc.gnu.org/bugzilla/>
2013-03-02 20:42 ` g_sauthoff at web dot de
2013-03-02 20:44 ` pinskia at gcc dot gnu.org
2013-11-10  5:49 ` pinskia at gcc dot gnu.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=20100721235305.13037.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).