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] PR22746, crash when running 32-bit objdump on corrupted file Date: Thu, 25 Jan 2018 11:50:00 -0000 [thread overview] Message-ID: <38e64b0ecc7f4ee64a02514b8d532782ac057fa2@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 38e64b0ecc7f4ee64a02514b8d532782ac057fa2 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: 38e64b0ecc7f4ee64a02514b8d532782ac057fa2 PR22746, crash when running 32-bit objdump on corrupted file Avoid unsigned int overflow by performing bfd_size_type multiplication. PR 22746 * elfcode.h (elf_object_p): Avoid integer overflow.
next reply other threads:[~2018-01-25 11:50 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-25 11:50 sergiodj+buildbot [this message] 2018-01-25 11:50 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-01-25 12:24 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-01-25 12:45 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-01-25 12:48 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-01-25 13:02 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-01-25 13:03 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-01-25 13:36 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2018-01-25 13:59 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-01-25 14:29 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2018-01-25 14:38 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-01-25 15:17 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-01-25 15:31 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-01-25 16:51 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-01-25 17:12 ` Failures on Debian-s390x-native-gdbserver-m64, " 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=38e64b0ecc7f4ee64a02514b8d532782ac057fa2@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).