public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos_odonell at mentor dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug dynamic-link/14379] shared object constructors are called in the wrong order
Date: Wed, 12 Sep 2012 02:11:00 -0000 [thread overview]
Message-ID: <bug-14379-131-5DVbZvELwE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14379-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14379
--- Comment #4 from Carlos O'Donell <carlos_odonell at mentor dot com> 2012-09-12 02:10:44 UTC ---
(In reply to comment #3)
> [marking as UNCONFIRMED because I don't think this is waiting for anything]
That's right, you've provided an example and we need someone to review the
example. Thanks for updating the ticket.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-09-12 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 19:12 [Bug dynamic-link/14379] New: " luto at mit dot edu
2012-07-21 16:29 ` [Bug dynamic-link/14379] " ppluzhnikov at google dot com
2012-07-24 1:41 ` carlos_odonell at mentor dot com
2012-07-24 15:21 ` luto at mit dot edu
2012-09-11 23:41 ` luto at mit dot edu
2012-09-12 2:11 ` carlos_odonell at mentor dot com [this message]
2012-12-04 0:00 ` carlos at systemhalted dot org
2014-06-17 18:57 ` fweimer at redhat dot com
2014-10-02 16:43 ` luto at mit dot edu
2014-10-02 16:45 ` luto at mit dot edu
2014-10-02 16:46 ` luto at mit dot edu
2022-08-29 9:46 ` [Bug dynamic-link/14379] shared object constructors are called in the wrong order (with interposition) 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-14379-131-5DVbZvELwE@http.sourceware.org/bugzilla/ \
--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).