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: improve enable error messages
Date: Fri, 09 Feb 2018 15:00:00 -0000 [thread overview]
Message-ID: <17ad2a4f466f22b7a75b5ebf8a68446bb328c40c@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 17ad2a4f466f22b7a75b5ebf8a68446bb328c40c ***
Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 17ad2a4f466f22b7a75b5ebf8a68446bb328c40c
btrace: improve enable error messages
Improve the error message when GDB fails to start recording branch trace.
This patch also removes a zero buffer size check for PT to align with BTS. The
buffer size can not be configured to be zero.
gdb/
* nat/linux-btrace.c (perf_event_pt_event_type): Improve error message.
Remove parameter and change return type. Update callers. Move it.
(linux_enable_bts, linux_enable_pt): Improve error message.
(linux_enable_pt): Remove zero buffer size check.
(linux_enable_btrace): Improve error messages. Remove NULL return
check.
next reply other threads:[~2018-02-09 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 15:00 sergiodj+buildbot [this message]
2018-02-09 15:00 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-09 17:39 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-09 20:13 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-02-09 20:26 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-09 20:35 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-09 20:46 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-09 20:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-09 20:53 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-02-09 21:01 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-09 22:19 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-02-09 22:36 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-10 1:38 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-02-10 17:24 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-10 19:36 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2018-02-10 22:19 ` Failures on Ubuntu-AArch64-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=17ad2a4f466f22b7a75b5ebf8a68446bb328c40c@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: link
Be 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).