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] Prevent memory access violations when attempting to parse an x86_64 PE binary containing corrupt unwind information.
Date: Tue, 13 Mar 2018 14:19:00 -0000 [thread overview]
Message-ID: <3e33b239450771394fa6c83b67b9de80169f35e8@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 3e33b239450771394fa6c83b67b9de80169f35e8 ***
Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 3e33b239450771394fa6c83b67b9de80169f35e8
Prevent memory access violations when attempting to parse an x86_64 PE binary containing corrupt unwind information.
PR 22113
incldue * coff/pe.h (struct pex64_unwind_info): Add a rawUnwindCodesEnd
field.
bfd * pei-x86_64.c (pex64_get_unwind_info): Change to a boolean
function. Add an end address parameter. Check access of the data
pointer to make sure that they do not extend beyond the end
address. Return FALSE if any check fails. Add the end address
pointer to the ui structure.
(pex64_xdata_print_uwd_codes): Check accesses of the raw unwind
codes to make sure that they do not extend beyond the end address
pointer. Print an error message and return immediately if any
check fails.
next reply other threads:[~2018-03-13 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 14:19 sergiodj+buildbot [this message]
2018-03-13 14:19 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-03-13 14:20 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-03-13 14:26 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-13 14:28 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-03-13 14:35 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-03-13 14:47 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-13 14:48 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-13 14:49 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-03-13 14:58 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot
2018-03-13 15:08 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2018-03-13 15:16 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-13 15:42 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-13 16:07 ` 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=3e33b239450771394fa6c83b67b9de80169f35e8@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).