public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj@redhat.com To: gdb-testers@sourceware.org Subject: Test results for commit d33501a51f46193387ff2d101752a9a878202f82 on branch master Date: Mon, 09 Feb 2015 13:12:00 -0000 [thread overview] Message-ID: <d33501a51f46193387ff2d101752a9a878202f82@kwanyin> (raw) *** TEST RESULTS FOR COMMIT d33501a51f46193387ff2d101752a9a878202f82 *** Author: Markus Metzger <markus.t.metzger@intel.com> Branch: master Commit: d33501a51f46193387ff2d101752a9a878202f82 record-btrace: add bts buffer size configuration option Allow the size of the branch trace ring buffer to be defined by the user. The specified buffer size will be used when BTS tracing is enabled for new threads. The obtained buffer size may differ from the requested size. The actual buffer size for the current thread is shown in the "info record" command. Bigger buffers mean longer traces, but also longer processing time. 2015-02-09 Markus Metzger <markus.t.metzger@intel.com> * btrace.c (parse_xml_btrace_conf_bts): Add size. (btrace_conf_bts_attributes): New. (btrace_conf_children): Add attributes. * common/btrace-common.h (btrace_config_bts): New. (btrace_config)<bts>: New. (btrace_config): Update comment. * nat/linux-btrace.c (linux_enable_btrace, linux_enable_bts): Use config. * features/btrace-conf.dtd: Increment version. Add size attribute to bts element. * record-btrace.c (set_record_btrace_bts_cmdlist, show_record_btrace_bts_cmdlist): New. (record_btrace_adjust_size, record_btrace_print_bts_conf, record_btrace_print_conf, cmd_set_record_btrace_bts, cmd_show_record_btrace_bts): New. (record_btrace_info): Call record_btrace_print_conf. (_initialize_record_btrace): Add commands. * remote.c: Add PACKET_Qbtrace_conf_bts_size enum. (remote_protocol_features): Add Qbtrace-conf:bts:size packet. (btrace_sync_conf): Synchronize bts size. (_initialize_remote): Add Qbtrace-conf:bts:size packet. * NEWS: Announce new commands and new packets. doc/ * gdb.texinfo (Branch Trace Configuration Format): Add size. (Process Record and Replay): Describe new set|show commands. (General Query Packets): Describe Qbtrace-conf:bts:size packet. testsuite/ * gdb.btrace/buffer-size: New. gdbserver/ * linux-low.c (linux_low_btrace_conf): Print size. * server.c (handle_btrace_conf_general_set): New. (hanle_general_set): Call handle_btrace_conf_general_set. (handle_query): Report Qbtrace-conf:bts:size as supported.
next reply other threads:[~2015-02-09 12:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-09 13:12 sergiodj [this message] 2015-02-09 13:35 ` Failures on Fedora-i686, " sergiodj 2015-02-09 14:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj 2015-02-09 14:06 ` Failures on Debian-x86_64-cc-with-index, " sergiodj 2015-02-09 14:26 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj 2015-02-09 14:38 ` Failures on Fedora-ppc64le-m64, " sergiodj 2015-02-09 16:52 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj 2015-02-09 17:32 ` Failures on Fedora-ppc64be-m64, " sergiodj 2015-02-09 17:49 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj 2015-02-09 18:16 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj
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=d33501a51f46193387ff2d101752a9a878202f82@kwanyin \ --to=sergiodj@redhat.com \ --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).