public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj@redhat.com
To: gdb-testers@sourceware.org
Subject: Test results for commit 03a91817f163986f10cb843f58e2f2cd9186e4f0 on branch master
Date: Tue, 10 Feb 2015 23:03:00 -0000 [thread overview]
Message-ID: <03a91817f163986f10cb843f58e2f2cd9186e4f0@kwanyin> (raw)
*** TEST RESULTS FOR COMMIT 03a91817f163986f10cb843f58e2f2cd9186e4f0 ***
Author: Nick Clifton <nickc@redhat.com>
Branch: master
Commit: 03a91817f163986f10cb843f58e2f2cd9186e4f0
Fixes for memory access violations triggered by running readelf on fuzzed binaries.
PR binutils/17531
* dwarf.c (process_debug_info): Zero the debug information array
since correct initialisation cannot be relied upon.
(process_cu_tu_index): Improve range checks.
next reply other threads:[~2015-02-10 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 23:03 sergiodj [this message]
2015-02-10 23:08 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj
2015-02-10 23:14 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj
2015-02-10 23:14 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj
2015-02-10 23:17 ` Failures on Fedora-ppc64le-m64, " sergiodj
2015-02-11 1:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj
2015-02-11 1:31 ` Failures on Fedora-ppc64be-m64, " sergiodj
2015-02-11 1:32 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj
2015-02-11 1:44 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj
2015-02-11 2:03 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj
2015-02-11 5:08 ` Failures on Debian-i686-cc-with-index, " sergiodj
2015-02-11 5:49 ` Failures on Debian-i686, " sergiodj
2015-02-11 6:55 ` Failures on Debian-i686-native-gdbserver, " sergiodj
2015-02-11 7:36 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj
2015-02-11 8:14 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj
2015-02-11 9:54 ` Failures on Debian-x86_64-m64, " sergiodj
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=03a91817f163986f10cb843f58e2f2cd9186e4f0@kwanyin \
--to=sergiodj@redhat.com \
--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).