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 a possible seg-fault in the section merging code, by always creating a padding buffer. Date: Thu, 16 Nov 2017 15:02:00 -0000 [thread overview] Message-ID: <38b28f7088057d70497de7312cd983ec8e408a76@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 38b28f7088057d70497de7312cd983ec8e408a76 *** Author: Nick Clifton <nickc@redhat.com> Branch: master Commit: 38b28f7088057d70497de7312cd983ec8e408a76 Prevent a possible seg-fault in the section merging code, by always creating a padding buffer. * merge.c (sec_merge_emit): Always create padding buffer. Add asserts to make sure that the buffer is long enough.
next reply other threads:[~2017-11-16 15:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-16 15:02 sergiodj+buildbot [this message] 2017-11-16 15:02 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master sergiodj+buildbot 2017-11-16 15:20 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-11-16 15:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-11-16 16:01 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-16 17:54 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-11-16 18:19 ` Failures on Ubuntu-AArch32-native-extended-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=38b28f7088057d70497de7312cd983ec8e408a76@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).