public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28453] ld.so segfaults when relocating x86 libstdc++.so compiled with -fno-plt
Date: Wed, 17 Nov 2021 14:10:11 +0000 [thread overview]
Message-ID: <bug-28453-131-tclEdrM8Wp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28453-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28453
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
I built libstdc++ with -fno-plt and
-Wl,--as-needed,-O1,--hash-style=gnu,-z,relro,-z,now
using bfd linker. I got
Dynamic section at offset 0x203c40 contains 29 entries:
Tag Type Name/Value
0x0000000000000001 (NEEDED) Shared library: [libm.so.6]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
0x0000000000000001 (NEEDED) Shared library: [ld-linux-x86-64.so.2]
0x0000000000000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x000000000000000e (SONAME) Library soname: [libstdc++.so.6]
0x000000000000000c (INIT) 0x99000
0x000000000000000d (FINI) 0x18de44
0x0000000000000019 (INIT_ARRAY) 0x1fb898
0x000000000000001b (INIT_ARRAYSZ) 96 (bytes)
0x000000000000001a (FINI_ARRAY) 0x1fb8f8
0x000000000000001c (FINI_ARRAYSZ) 8 (bytes)
0x000000006ffffef5 (GNU_HASH) 0x2a8
0x0000000000000005 (STRTAB) 0x2d120
0x0000000000000006 (SYMTAB) 0x9000
0x000000000000000a (STRSZ) 301565 (bytes)
0x000000000000000b (SYMENT) 24 (bytes)
0x0000000000000003 (PLTGOT) 0x204e50
0x0000000000000007 (RELA) 0x7a340
0x0000000000000008 (RELASZ) 124464 (bytes)
0x0000000000000009 (RELAENT) 24 (bytes)
0x000000006ffffffc (VERDEF) 0x79b38
0x000000006ffffffd (VERDEFNUM) 48
0x0000000000000018 (BIND_NOW)
0x000000006ffffffb (FLAGS_1) Flags: NOW
0x000000006ffffffe (VERNEED) 0x7a1d0
0x000000006fffffff (VERNEEDNUM) 4
0x000000006ffffff0 (VERSYM) 0x76b1e
0x000000006ffffff9 (RELACOUNT) 892
0x0000000000000000 (NULL) 0x0
Please pass "-Wl,--verbose" to GCC to identify the linker used.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-17 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 0:45 [Bug dynamic-link/28453] New: " alex_y_xu at yahoo dot ca
2021-10-25 1:23 ` [Bug dynamic-link/28453] " sam at gentoo dot org
2021-11-17 8:43 ` fweimer at redhat dot com
2021-11-17 13:09 ` hjl.tools at gmail dot com
2021-11-17 13:31 ` alex_y_xu at yahoo dot ca
2021-11-17 14:10 ` hjl.tools at gmail dot com [this message]
2021-11-17 14:17 ` fweimer at redhat dot com
2021-11-17 14:39 ` alex_y_xu at yahoo dot ca
2021-11-17 14:58 ` hjl.tools at gmail dot com
2021-11-17 14:59 ` hjl.tools at gmail dot com
2021-11-17 16:05 ` hjl.tools at gmail dot com
2021-12-09 17:47 ` alex_y_xu at yahoo dot ca
2021-12-09 17:51 ` alex_y_xu at yahoo dot ca
2021-12-10 2:32 ` hjl.tools at gmail dot com
2021-12-10 16:02 ` alex_y_xu at yahoo dot ca
2021-12-10 19:55 ` hjl.tools at gmail dot com
2021-12-28 17:32 ` alex_y_xu at yahoo dot ca
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-28453-131-tclEdrM8Wp@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).