From: "matoro_bugzilla_glibc at matoro dot tk" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/29112] New: run-elflint-self.sh and run-reverse-sections-self.sh fail on ia64 with "PLTGOT value must point into loaded segment"
Date: Mon, 02 May 2022 01:40:58 +0000 [thread overview]
Message-ID: <bug-29112-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29112
Bug ID: 29112
Summary: run-elflint-self.sh and run-reverse-sections-self.sh
fail on ia64 with "PLTGOT value must point into loaded
segment"
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: matoro_bugzilla_glibc at matoro dot tk
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
In elfutils unit tests, the following tests fail on ia64:
FAIL: run-elflint-self.sh
=========================
section [21] '.dynamic': entry 16: PLTGOT value must point into loaded segment
*** failure in
/var/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187-.ia64/src/elflint
--quiet --gnu-ld /var/tmp/portage/dev-libs/elfutils-0.187/work/elf>
section [20] '.dynamic': entry 15: PLTGOT value must point into loaded segment
*** failure in
/var/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187-.ia64/src/elflint
--quiet --gnu-ld /var/tmp/portage/dev-libs/elfutils-0.187/work/elf>
section [21] '.dynamic': entry 16: PLTGOT value must point into loaded segment
*** failure in
/var/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187-.ia64/src/elflint
--quiet --gnu-ld /var/tmp/portage/dev-libs/elfutils-0.187/work/elf>
section [21] '.dynamic': entry 15: PLTGOT value must point into loaded segment
*** failure in
/var/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187-.ia64/src/elflint
--quiet --gnu-ld /var/tmp/portage/dev-libs/elfutils-0.187/work/elf>
section [21] '.dynamic': entry 15: PLTGOT value must point into loaded segment
*** failure in
/var/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187-.ia64/src/elflint
--quiet --gnu-ld /var/tmp/portage/dev-libs/elfutils-0.187/work/elf>
FAIL run-elflint-self.sh (exit status: 1)
FAIL: run-reverse-sections-self.sh
==================================
copy_elf:
/var/tmp/portage/dev-libs/elfutils-0.187/work/elfutils-0.187-.ia64/src/addr2line
-> addr2line.rev (read,reverse)
setshstrndx: 41
Swapping offsets of section 31 and 32
Swapping offsets of section 33 and 34
Swapping offsets of section 35 and 36
Swapping offsets of section 37 and 38
Swapping offsets of section 40 and 41
section [21] '.dynamic': entry 16: PLTGOT value must point into loaded segment
FAIL run-reverse-sections-self.sh (exit status: 1)
This is not a regression, and has been observed since at least elfutils 0.158
(https://bugs.gentoo.org/501630) and still occurs on elfutils 0.187.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2022-05-02 1:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-29112-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).