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] New: segfault in ld-linux after aug 2022
Date: Wed, 18 Jan 2023 12:46:26 +0000 [thread overview]
Message-ID: <bug-30020-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30020
Bug ID: 30020
Summary: segfault in ld-linux after aug 2022
Product: glibc
Version: 2.35
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: petelomax at ymail dot com
Target Milestone: ---
My manually built elf x64 file started segfaulting somewhere deep inside
ld-linux in August 2022, exact same had been fine for 10 months.
You can download the offending file (a single plain 4MB ELF x64) from
http://phix.x10.mx/p64
Oddly running /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 ./p64 works fine,
ie the exact same files but loaded the other way round.
One user upgraded their Linux kernel to 5.4.0-131-generic, which fixed the
issue, but suspects 5.15.x won’t work.
I'm still (5 months on) trying to find a fix. Apparently it wasn't the DT_HASH
thing. The ELF headers are as simple as I could make them, should they need
changing I need at the very least some clues.
Let me know if a 1.3K sys_write "It works!" with an easy to read byte-by-byte
300 line listing would help any (no idea why it would), alas not input for
gcc/ld/etc.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-01-18 12:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 12:46 petelomax at ymail dot com [this message]
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
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@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).