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] Make output_thread_groups take an std::vector<int> Date: Fri, 17 Nov 2017 18:49:00 -0000 [thread overview] Message-ID: <5c632425957f0150a0d5d1e747f0425f74622132@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 5c632425957f0150a0d5d1e747f0425f74622132 *** Author: Simon Marchi <simon.marchi@polymtl.ca> Branch: master Commit: 5c632425957f0150a0d5d1e747f0425f74622132 Make output_thread_groups take an std::vector<int> A simple replacement of VEC with std::vector. gdb/ChangeLog: * breakpoint.c (output_thread_groups): Take an std::vector. (print_one_breakpoint_location): Adjust.
next reply other threads:[~2017-11-17 18:49 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-17 18:49 sergiodj+buildbot [this message] 2017-11-17 18:49 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot 2017-11-17 18:55 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-11-17 18:58 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-11-17 18:59 ` Failures on Fedora-i686, " sergiodj+buildbot 2017-11-17 19:12 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2017-11-17 19:15 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-17 19:26 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-11-17 21:39 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-11-17 22:03 ` Failures on Ubuntu-AArch32-native-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=5c632425957f0150a0d5d1e747f0425f74622132@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).