public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Re: Usage of unitialized heap in tic4x_print_cond Date: Sun, 29 Dec 2019 23:41:00 -0000 [thread overview] Message-ID: <2c5b6e1a1c406cbe06e2d6f77861764ebd01b9ce@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 2c5b6e1a1c406cbe06e2d6f77861764ebd01b9ce *** commit 2c5b6e1a1c406cbe06e2d6f77861764ebd01b9ce Author: Alan Modra <amodra@gmail.com> AuthorDate: Mon Dec 30 09:19:25 2019 +1030 Commit: Alan Modra <amodra@gmail.com> CommitDate: Mon Dec 30 09:35:29 2019 +1030 Re: Usage of unitialized heap in tic4x_print_cond PR 25319 * tic4x-dis.c (tic4x_print_cond): Correct order of xcalloc args. diff --git a/opcodes/ChangeLog b/opcodes/ChangeLog index bde9b92166..5021447c18 100644 --- a/opcodes/ChangeLog +++ b/opcodes/ChangeLog @@ -1,3 +1,8 @@ +2019-12-30 Alan Modra <amodra@gmail.com> + + PR 25319 + * tic4x-dis.c (tic4x_print_cond): Correct order of xcalloc args. + 2019-12-29 Alan Modra <amodra@gmail.com> * sparc-dis.c (SEX): Don't use left and right shift to sign extend. diff --git a/opcodes/tic4x-dis.c b/opcodes/tic4x-dis.c index 01cfa1e060..e058fdc9f8 100644 --- a/opcodes/tic4x-dis.c +++ b/opcodes/tic4x-dis.c @@ -277,7 +277,7 @@ tic4x_print_cond (struct disassemble_info *info, unsigned int cond) if (condtable == NULL) { - condtable = xcalloc (sizeof (tic4x_cond_t *), 32); + condtable = xcalloc (32, sizeof (tic4x_cond_t *)); for (i = 0; i < tic4x_num_conds; i++) condtable[tic4x_conds[i].cond] = (tic4x_cond_t *)(tic4x_conds + i); }
next reply other threads:[~2019-12-29 23:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-29 23:41 gdb-buildbot [this message] 2019-12-29 23:41 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, branch master gdb-buildbot 2019-12-29 23:49 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-12-29 23:49 ` Failures on Fedora-i686, " gdb-buildbot 2019-12-29 23:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2019-12-30 0:22 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2019-12-30 0:37 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2019-12-30 3:35 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-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=2c5b6e1a1c406cbe06e2d6f77861764ebd01b9ce@gdb-build \ --to=gdb-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).