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, gdbserver: check btrace target pointers Date: Thu, 01 Mar 2018 11:41:00 -0000 [thread overview] Message-ID: <b1223e789040e9e8cdc6869a8a1fd1fd7acc109d@gdb-build> (raw) *** TEST RESULTS FOR COMMIT b1223e789040e9e8cdc6869a8a1fd1fd7acc109d *** Author: Markus Metzger <markus.t.metzger@intel.com> Branch: master Commit: b1223e789040e9e8cdc6869a8a1fd1fd7acc109d btrace, gdbserver: check btrace target pointers By removing the supports_btrace gdbserver target method we relied on GDB trying to enable branch tracing and failing on the attempt. For targets that do not provide the btrace methods, however, an initial request from GDB for the branch trace configuration to detect whether gdbserver is already recording resulted in a protocol error. Have the btrace target methods throw a "Target does not suppor branch tracing" error and be prepared to handle exceptions in all functions that call btrace target methods. We therefore turn the target_* macros into static inline functions. Also remove the additional btrace target method checks that resulted in the above protocol error. Thanks to Maciej W. Rozycki <macro@mips.com> for reporting this. gdbserver/ * target.h (target_enable_btrace, target_disable_btrace) (target_read_btrace, target_read_btrace_conf): Turn macro into inline function. Throw error if target method is not defined. * server.c (handle_qxfer_btrace, handle_qxfer_btrace_conf): Remove check for btrace target method. Be prepared to handle exceptions from btrace target methods.
next reply other threads:[~2018-03-01 11:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-01 11:41 sergiodj+buildbot [this message] 2018-03-01 11:41 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-03-01 11:53 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-01 12:03 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-01 12:08 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-01 12:16 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-03-01 12:20 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-03-01 12:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-01 12:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-01 12:26 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-03-01 12:55 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-01 13:21 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-03-01 21:27 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-03-01 21:42 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-01 21:56 ` Failures on Debian-s390x-native-gdbserver-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=b1223e789040e9e8cdc6869a8a1fd1fd7acc109d@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).