public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Ignore degenerate PT_LOAD segments
Date: Sat, 17 Feb 2018 00:02:00 -0000 [thread overview]
Message-ID: <325ba6fb34be799c885fad9287d883e86b835c84@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 325ba6fb34be799c885fad9287d883e86b835c84 ***
Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 325ba6fb34be799c885fad9287d883e86b835c84
Ignore degenerate PT_LOAD segments
Fixes a failure triggered by -z separate-code. p_memsz is tested
rather than p_filesz for objcopy --only-keep-debug where p_filesz is
set to zero.
PR 22845
* elf.c (assign_file_positions_for_non_load_sections): Ignore
degenerate zero size PT_LOAD segments when finding one overlapping
the PT_GNU_RELRO segment.
next reply other threads:[~2018-02-17 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 0:02 sergiodj+buildbot [this message]
2018-02-17 0:02 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-17 0:16 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-17 0:21 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-17 0:46 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-17 0:54 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-17 0:54 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-02-17 0:58 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-18 1:58 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-01 15:27 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
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=325ba6fb34be799c885fad9287d883e86b835c84@gdb-build \
--to=sergiodj+buildbot@sergiodj.net \
--cc=gdb-testers@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).