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: prepare for throwing exceptions when enabling btrace
Date: Fri, 09 Feb 2018 14:22:00 -0000 [thread overview]
Message-ID: <5c3284c1ec2edc28b0697532fd094d93d5ecf31b@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 5c3284c1ec2edc28b0697532fd094d93d5ecf31b ***
Author: Markus Metzger <markus.t.metzger@intel.com>
Branch: master
Commit: 5c3284c1ec2edc28b0697532fd094d93d5ecf31b
btrace: prepare for throwing exceptions when enabling btrace
We indicate success or failure for enabling branch tracing via the pointer
return value. Depending on the type of error, errno may provide additional
information.
Prepare for using exceptions with more descriptive error messages by using smart
pointers and objects with automatic destruction to hold intermediate results.
gdb/
* nat/linux-btrace.c: Include scoped_fd.h and scoped_mmap.h.
(perf_event_pt_event_type): Use gdb_file_up.
(linux_enable_bts, linux_enable_pt): Use gdb::unique_xmalloc_ptr,
scoped_fd, and scoped_mmap.
next reply other threads:[~2018-02-09 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 14:22 sergiodj+buildbot [this message]
2018-02-09 14:22 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-02-09 16:13 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2018-02-09 17:35 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-09 17:48 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-02-09 17:48 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-02-09 17:50 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-02-09 18:10 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-02-09 18:25 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-02-09 18:30 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-02-09 22:39 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2018-02-09 23:15 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2018-02-10 10:25 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-02-10 11:16 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-02-10 11:59 ` 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=5c3284c1ec2edc28b0697532fd094d93d5ecf31b@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).