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] btrace: fix output of "set record btrace" Date: Fri, 13 Apr 2018 09:59:00 -0000 [thread overview] Message-ID: <b85310e1ec0419c4e1ca091cdd48f7597ebbefd3@gdb-build> (raw) *** TEST RESULTS FOR COMMIT b85310e1ec0419c4e1ca091cdd48f7597ebbefd3 *** Author: Markus Metzger <markus.t.metzger@intel.com> Branch: master Commit: b85310e1ec0419c4e1ca091cdd48f7597ebbefd3 btrace: fix output of "set record btrace" Instead of giving a message that "set record btrace" needs a sub-command, GDB crashed. Fix it. A regression test comes with the next patch. gdb/ * record-btrace.c (cmd_set_record_btrace): Print sub-commands.
next reply other threads:[~2018-04-13 9:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-13 9:59 sergiodj+buildbot [this message] 2018-04-13 9:59 ` *** COMPILATION FAILED *** Failures on NetBSD-x86_64-m64, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-13 10:06 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-04-13 10:09 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-04-13 10:11 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-04-13 10:22 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-04-13 10:28 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-13 10:29 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-04-13 10:32 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-13 10:35 ` Failures on Fedora-x86_64-native-gdbserver-m64, branch master sergiodj+buildbot 2018-04-13 11:00 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-04-13 12:47 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-13 13:30 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-04-13 14:13 ` 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=b85310e1ec0419c4e1ca091cdd48f7597ebbefd3@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).