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 an illegal memory access in gprof by ensuring that string tables for aout format files are always zero-terminated. Date: Mon, 23 Apr 2018 12:15:00 -0000 [thread overview] Message-ID: <bf82069dce1b1a88560e5d7320342c78372b627e@gdb-build> (raw) *** TEST RESULTS FOR COMMIT bf82069dce1b1a88560e5d7320342c78372b627e *** Author: Nick Clifton <nickc@redhat.com> Branch: master Commit: bf82069dce1b1a88560e5d7320342c78372b627e Prevent an illegal memory access in gprof by ensuring that string tables for aout format files are always zero-terminated. PR 23056 * aoutx.h (aout_get_external_symbols): Allocate an extra byte at the end of the string table, and zero it.
next reply other threads:[~2018-04-23 12:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-23 12:15 sergiodj+buildbot [this message] 2018-04-23 12:14 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-04-23 12:20 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-04-23 12:22 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-04-23 12:30 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-04-23 12:32 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-04-23 12:34 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-04-23 12:40 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-04-23 12:43 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-23 12:48 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-23 13:23 ` Failures on Debian-s390x-native-extended-gdbserver-m64, branch master sergiodj+buildbot 2018-04-23 13:27 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-04-23 14:42 ` 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=bf82069dce1b1a88560e5d7320342c78372b627e@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: linkBe 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).