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/17711] copy relocations against protected symbols don't work
Date: Sun, 14 Dec 2014 15:06:00 -0000 [thread overview]
Message-ID: <bug-17711-131-pCq5JtBaPQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17711-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17711
--- Comment #1 from Ondrej Bilka <neleai at seznam dot cz> ---
On Sun, Dec 14, 2014 at 12:43:50PM +0000, hjl.tools at gmail dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17711
>
> Bug ID: 17711
> Summary: copy relocations against protected symbols don't work
> Product: glibc
> Version: 2.21
> Status: NEW
> Severity: normal
> Priority: P2
> Component: dynamic-link
> Assignee: unassigned at sourceware dot org
> Reporter: hjl.tools at gmail dot com
>
> On Linux/x86-64, I got
>
> [hjl@gnu-tools-1 pr15228]$ cat x.c
> extern int a;
>
> extern void bar (void);
>
> int main()
> {
> bar ();
> if (a != 30)
> __builtin_abort();
> return 0;
> }
> [hjl@gnu-tools-1 pr15228]$ cat bar.c
> int a;
>
> __attribute__((visibility("protected"))) int a;
>
> void
> bar ()
> {
> a = 30;
> }
> [hjl@gnu-tools-1 pr15228]$ make all
> gcc -B/bin/ -c -o x.o x.c
> gcc -B/bin/ -fPIC -c -o bar.o bar.c
> ./ld -shared -o libbar.so bar.o
> gcc -B/bin/ -o x x.o libbar.so -Wl,-rpath,.
> ./x
> make: *** [all] Aborted (core dumped)
> [hjl@gnu-tools-1 pr15228]$
>
What commit does git bisect report?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-14 15:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 12:43 [Bug dynamic-link/17711] New: " hjl.tools at gmail dot com
2014-12-14 15:05 ` Ondřej Bílka
2014-12-14 15:06 ` neleai at seznam dot cz [this message]
2014-12-14 15:14 ` [Bug dynamic-link/17711] " hjl.tools at gmail dot com
2014-12-14 20:24 ` hjl.tools at gmail dot com
2014-12-15 0:58 ` hjl.tools at gmail dot com
2014-12-17 16:27 ` hjl.tools at gmail dot com
2014-12-17 21:25 ` hjl.tools at gmail dot com
2015-02-27 21:25 ` hjl.tools at gmail dot com
2015-02-27 22:14 ` cvs-commit at gcc dot gnu.org
2015-02-27 22:16 ` hjl.tools at gmail dot com
2015-03-05 23:20 ` hjl.tools at gmail dot com
2015-03-05 23:50 ` cvs-commit at gcc dot gnu.org
2015-03-06 12:59 ` cvs-commit at gcc dot gnu.org
2015-03-06 13:02 ` cvs-commit at gcc dot gnu.org
2015-03-06 19:39 ` cvs-commit at gcc dot gnu.org
2015-03-06 21:26 ` cvs-commit at gcc dot gnu.org
2015-03-06 22:56 ` hjl.tools at gmail dot com
2015-03-06 23:43 ` cvs-commit at gcc dot gnu.org
2015-03-07 0:59 ` cvs-commit at gcc dot gnu.org
2015-03-07 1:08 ` cvs-commit at gcc dot gnu.org
2015-03-07 14:26 ` cvs-commit at gcc dot gnu.org
2015-03-27 17:21 ` hjl.tools at gmail dot com
2015-03-31 12:17 ` cvs-commit at gcc dot gnu.org
2015-03-31 12:22 ` cvs-commit at gcc dot gnu.org
2015-04-01 0:02 ` cvs-commit at gcc dot gnu.org
2015-04-01 0:05 ` cvs-commit at gcc dot gnu.org
2015-04-01 0:07 ` cvs-commit at gcc dot gnu.org
2015-04-01 0:19 ` cvs-commit at gcc dot gnu.org
2015-04-01 0:28 ` cvs-commit at gcc dot gnu.org
2015-07-11 19:46 ` neleai at seznam dot cz
2015-07-24 9:08 ` cvs-commit at gcc dot gnu.org
2015-08-02 3:55 ` cvs-commit 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=bug-17711-131-pCq5JtBaPQ@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).