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] Segfault on phdrs allocated but not created
Date: Mon, 26 Feb 2018 01:53:00 -0000	[thread overview]
Message-ID: <6838f2bed6459514c1b0c549e6aa3fc7dbb1d7ec@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 6838f2bed6459514c1b0c549e6aa3fc7dbb1d7ec ***

Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 6838f2bed6459514c1b0c549e6aa3fc7dbb1d7ec

Segfault on phdrs allocated but not created

A number of ARM tests show results like:
ld-new: no address assigned to the veneers output section .gnu.sgstubs
ld-new: can not size stub section: invalid operation
ld-new: warning: cannot find entry symbol _start; defaulting to 0000000000010074
ld-new: tmpdir/cmse-veneers-no-gnu_sgstubs: warning: allocated section `.text' not in segment
Segmentation fault
PASS: Secure gateway veneers: no .gnu.sgstubs section

The PASS despite the segv shows the danger of using "#..." to match
error output.  This patch doesn't try to fix the testuite, but does
prevent the segfault.

	* elf.c (assign_file_positions_except_relocs): Don't segfault
	when actual number of phdrs is less than allocated.  Delete
	outdated comment.  Formatting.


             reply	other threads:[~2018-02-26  1:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  1:53 sergiodj+buildbot [this message]
2018-02-26  1:53 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-26  3:19 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-26  7:28 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-26  7:34 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-26  7:49 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-26  7:56 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-02-26  8:11 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-26 19:54 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-26 20:59 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-02-26 21:42 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-03-01 14:24 ` Failures on Debian-s390x-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=6838f2bed6459514c1b0c549e6aa3fc7dbb1d7ec@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).