public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "petelomax at ymail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/30020] segfault in ld-linux after aug 2022 Date: Mon, 13 Feb 2023 19:30:38 +0000 [thread overview] Message-ID: <bug-30020-131-QKufpr4xzJ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30020-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30020 --- Comment #4 from Pete Lomax <petelomax at ymail dot com> --- Thank you, that is a massive step in the right direction, I think. Yes, that is what success should look like. I had (and meant it): Size of section headers: 64 (bytes) Number of section headers: 0 (64) Previous versions of readelf (I just checked, 3.5.0-54-generic) did not mistreat that 0 as 64. Anyway, I patched that e_shentsize to 0 which got readelf down to 2 complaints (vs 0 previously): readelf: Error: Size (0xb0) of section <no-strings> is not a multiple of its sh_entsize (0x10) readelf: Error: Corrupt DT_SYMTAB dynamic entry I've also got: LOAD 0x0000000000000228 0x0000000000400228 0x0000000000400228 and patching away that 40 made readelf happier, but spannered ld-linux-x86-64.so.2 ./p64 So, while that was probably wrong, it made readelf show the 10 dynamic section entries it used to, along with an 11th (NULL) which it never did before, and (also new) followed by ten times: 0000004004b0 000100000001 R_X86_64_64 readelf: Error: bad symbol index: 00000001 in reloc PS: There really are no section headers, and there never was any debug info to be stripped. These headers all worked perfectly for years before August 2022. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-13 19:30 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-18 12:46 [Bug dynamic-link/30020] New: " petelomax at ymail dot com 2023-01-19 11:47 ` [Bug dynamic-link/30020] " petelomax at ymail dot com 2023-02-12 12:52 ` petelomax at ymail dot com 2023-02-13 14:23 ` adhemerval.zanella at linaro dot org 2023-02-13 19:30 ` petelomax at ymail dot com [this message] 2023-02-15 17:45 ` petelomax at ymail dot com 2023-02-15 17:51 ` adhemerval.zanella at linaro dot org 2023-02-15 18:38 ` petelomax at ymail dot com 2023-02-15 19:57 ` adhemerval.zanella at linaro dot org 2023-02-16 11:36 ` petelomax at ymail dot com 2023-02-16 11:59 ` adhemerval.zanella at linaro dot org 2023-02-16 22:03 ` petelomax at ymail dot com 2023-02-16 22:33 ` petelomax at ymail dot com 2023-02-16 22:52 ` petelomax at ymail dot com 2023-02-17 12:14 ` adhemerval.zanella at linaro dot org 2023-02-20 18:26 ` petelomax at ymail dot com 2023-02-20 18:39 ` petelomax at ymail dot com 2023-02-20 19:09 ` adhemerval.zanella at linaro dot org 2023-02-21 10:26 ` 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-30020-131-QKufpr4xzJ@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: linkBe 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).