public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mh-sourceware at glandium dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug dynamic-link/14341] Dynamic linker crash when DT_JMPREL and DT_REL{,A} are not contiguous
Date: Tue, 10 Jul 2012 08:27:00 -0000 [thread overview]
Message-ID: <bug-14341-131-ysZcqsxc4f@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14341-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14341
--- Comment #9 from Mike Hommey <mh-sourceware at glandium dot org> 2012-07-10 08:27:29 UTC ---
(In reply to comment #8)
> Slowing down the dynamic linker unnecessarily is a bad idea.
Does it make any kind of significant difference in the present case? We're
looking at a couple instructions, once per library.
Moreover, there's a discrepancy between the behaviour with RTLD_BIND_NOW set or
not.
--
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-07-10 8:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 8:55 [Bug dynamic-link/14341] New: " mh-sourceware at glandium dot org
2012-07-09 11:12 ` [Bug dynamic-link/14341] " aj at suse dot de
2012-07-09 16:05 ` carlos_odonell at mentor dot com
2012-07-09 16:14 ` mh-sourceware at glandium dot org
2012-07-09 19:21 ` carlos_odonell at mentor dot com
2012-07-09 19:22 ` carlos_odonell at mentor dot com
2012-07-10 7:55 ` mh-sourceware at glandium dot org
2012-07-10 7:59 ` jakub at redhat dot com
2012-07-10 8:03 ` mh-sourceware at glandium dot org
2012-07-10 8:17 ` jakub at redhat dot com
2012-07-10 8:27 ` mh-sourceware at glandium dot org [this message]
2012-12-03 23:59 ` carlos at systemhalted dot org
2014-06-13 14:01 ` fweimer at redhat dot com
2014-08-21 15:58 ` mips32r2 at gmail dot com
2015-08-19 12:52 ` cvs-commit at gcc dot gnu.org
2015-08-19 13:02 ` cvs-commit at gcc dot gnu.org
2015-08-19 13:03 ` hjl.tools at gmail dot com
2021-11-22 1:08 ` zacmanken at gmail dot com
2021-11-22 1:09 ` zacmanken at gmail dot com
2021-11-22 1:09 ` zacmanken at gmail dot com
2021-11-22 12:25 ` adhemerval.zanella at linaro dot 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=bug-14341-131-ysZcqsxc4f@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).