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] PR22758, FAIL: Run pr22393-2
Date: Tue, 30 Jan 2018 08:44:00 -0000	[thread overview]
Message-ID: <76cb3a89a6615cf3418fa1efe8268bf6673a5c8a@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 76cb3a89a6615cf3418fa1efe8268bf6673a5c8a ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 76cb3a89a6615cf3418fa1efe8268bf6673a5c8a

PR22758, FAIL: Run pr22393-2

We can't map different disk pages into the same memory page; The last
page mapped will simply overwrite any previous pages.  The
executable/non-executable new_segment test ignored this fact, leading
to a ld.so segfault on hppa when .dynamic is overwritten with zeros.

This patch moves existing tests for demand paging with lma on the same
memory page, to a new test performed before any case where we want a
new segment due to protection or loadable conflicts.

	PR 22758
	* elf.c (_bfd_elf_map_sections_to_segments): Don't start a new
	segment when demand paged with lma on the same page.  Test this
	before load/non-load, executable/non-executable,
	writable/non-writable tests and simplify.  Delete bogus relro
	condition in writable/non-writable test.  Delete outdated
	comment.  Formatting.


             reply	other threads:[~2018-01-30  8:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30  8:44 sergiodj+buildbot [this message]
2018-01-30  8:44 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-01-30  8:45 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-01-30  8:49 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-01-30  8:51 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-01-30  8:52 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-01-30  8:52 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-30  9:09 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-01-30  9:12 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-30  9:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-30  9:16 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-01-30  9:29 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-30  9:45 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-01-30 10:37 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-01-30 11:29 ` Failures on Ubuntu-AArch32-m32, " 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=76cb3a89a6615cf3418fa1efe8268bf6673a5c8a@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).