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, 20 Feb 2023 19:09:20 +0000 [thread overview]
Message-ID: <bug-30020-131-TNbclZG3kD@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 #17 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Pete Lomax from comment #15)
> Got it! It seems simply that p_align is now more strictly applied (fair
> enough, I guess). Many thanks, I've updated the binary at
> http://phix.x10.mx/p64 in case you still need it.
>
> There is one small matter remaining, readelf -a still displays these errors:
>
> readelf: Error: Size (0xb0) of section <no-strings> is not a multiple of its
> sh_entsize (0x10)
> readelf: Error: Corrupt DT_SYMTAB dynamic entry
>
> My best guess for that is it is comparing the number of entries in the
> Dynamic Link Info with the number of entries in the Symbol Table, for
> reasons that utterly escape me. It may also be "entries of 16 bytes per vs.
> entries of 24 bytes per", but I'm not sure.
>
> It also says "There are no sections in this file." which is correct, so I
> guessed it must be somehow faking a section, and indeed I can see that it is
> - search readelf.c for "overkill".
> I could live with this, but would rather know whether there is something I
> could do better.
> I've still got lots of work to do, but the original crisis is now officially
> over, and of course words are somehow completely inadequate to express my
> gratitude for all your help.
So I take this is not a glibc issue in the end then. I will this bug as
NOTABUG then.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-20 19:09 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
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 [this message]
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-TNbclZG3kD@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).