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] Catch integer overflows/underflows when parsing corrupt DWARF FORM blocks.
Date: Wed, 28 Feb 2018 12:18:00 -0000 [thread overview]
Message-ID: <12c963421d045a127c413a0722062b9932c50aa9@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 12c963421d045a127c413a0722062b9932c50aa9 ***
Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 12c963421d045a127c413a0722062b9932c50aa9
Catch integer overflows/underflows when parsing corrupt DWARF FORM blocks.
PR 22895
PR 22893
* dwarf2.c (read_n_bytes): Replace size parameter with dwarf_block
pointer. Drop unused abfd parameter. Check the size of the block
before initialising the data field. Return the end pointer if the
size is invalid.
(read_attribute_value): Adjust invocations of read_n_bytes.
next reply other threads:[~2018-02-28 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 12:18 sergiodj+buildbot [this message]
2018-02-28 12:18 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-28 12:34 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-28 13:27 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-28 13:38 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-02-28 13:44 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-28 13:54 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-28 13:57 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-01 0:01 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-01 0:52 ` 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=12c963421d045a127c413a0722062b9932c50aa9@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).