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] PR22169, heap-based buffer overflow in read_1_byte
Date: Sun, 24 Sep 2017 08:08:00 -0000 [thread overview]
Message-ID: <515f23e63c0074ab531bc954f84ca40c6281a724@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 515f23e63c0074ab531bc954f84ca40c6281a724 ***
Author: Alan Modra <amodra@gmail.com>
Branch: master
Commit: 515f23e63c0074ab531bc954f84ca40c6281a724
PR22169, heap-based buffer overflow in read_1_byte
The .debug_line header length field doesn't include the length field
itself, ie. it's the size of the rest of .debug_line.
PR 22169
* dwarf2.c (decode_line_info): Correct .debug_line unit_length check.
next reply other threads:[~2017-09-24 7:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 8:08 sergiodj+buildbot [this message]
2017-09-24 8:08 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-09-24 8:52 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-09-24 9:05 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-09-24 9:09 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-09-24 9:16 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-09-24 9:21 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-09-24 9:24 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-09-24 10:00 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-09-24 10:04 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-09-24 10:25 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-09-24 10:54 ` Failures on Ubuntu-AArch32-native-gdbserver-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=515f23e63c0074ab531bc954f84ca40c6281a724@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).