public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <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 14:23:34 +0000 [thread overview] Message-ID: <bug-30020-131-A8US1jzUud@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30020-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30020 Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #3 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> --- With glibc master I see: $ ./testrun.sh ./p64 Phix hybrid interpreter/compiler. Version 1.0.1 (64 bit Linux) Copyright Pete Lomax 2006..2016 Enter ? for options or filename to execute: Is it the expected output? However, running through execve the kernel shows the binary can not be loaded: kernel: Code: ff ff 00 45 31 db 48 8d 15 c9 ac 00 00 4c 8d 05 46 8f 01 00 4c 8d 2d 1f 8f 01 00 49 89 c2 48 8d 58 ff 48 89 f8 49> kernel: p64[54765]: segfault at 0 ip 00007fc7ce59c350 sp 00007fffd17839c0 error 4 in ld-linux-x86-64.so.2[7fc7ce57c000+2a000] So I am not sure it is really a glibc error, the binary is also stripped and not fully conformant (readelf -a show a lot of bogus information), so it is really difficult to debug. I think what might be happening is kernel ELF binfmt is seeing some unexpected and thus throwing the error. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-13 14:23 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 [this message] 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-A8US1jzUud@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).