public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/13818] Bogus LD_PROFILE will cause application to segfault
Date: Mon, 27 May 2013 09:26:00 -0000 [thread overview]
Message-ID: <bug-13818-131-Y2N4LyLvei@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13818-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13818
Alexander Monakov <amonakov at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |amonakov at gmail dot com
Resolution|--- |DUPLICATE
--- Comment #5 from Alexander Monakov <amonakov at gmail dot com> ---
This was independently discovered, filed and fixed as an LD_AUDIT bug 14831.
*** This bug has been marked as a duplicate of bug 14831 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-27 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 19:06 [Bug dynamic-link/13818] New: " law at redhat dot com
2012-03-22 12:56 ` [Bug dynamic-link/13818] " carlos_odonell at mentor dot com
2012-03-22 16:40 ` ppluzhnikov at google dot com
2012-04-06 20:33 ` aj at suse dot de
2012-04-10 5:00 ` law at redhat dot com
2012-07-26 4:41 ` law at redhat dot com
2012-07-26 7:05 ` schwab@linux-m68k.org
2012-11-29 15:55 ` carlos_odonell at mentor dot com
2012-12-03 23:58 ` carlos at systemhalted dot org
2013-05-27 9:26 ` amonakov at gmail dot com [this message]
2014-06-26 14:02 ` 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-13818-131-Y2N4LyLvei@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).