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 6f9b84910f8cabf565598f499258bbea51cc06d4 on branch master Date: Tue, 17 Feb 2015 18:00:00 -0000 [thread overview] Message-ID: <6f9b84910f8cabf565598f499258bbea51cc06d4@kwanyin> (raw) *** TEST RESULTS FOR COMMIT 6f9b84910f8cabf565598f499258bbea51cc06d4 *** Author: Jose E. Marchesi <jose.marchesi@oracle.com> Branch: master Commit: 6f9b84910f8cabf565598f499258bbea51cc06d4 Adapt `info probes' to support printing probes of different types. A "probe type" (backend for the probe abstraction implemented in probe.[ch]) can extend the information printed by `info probes' by defining additional columns. This means that when `info probes' is used to print all the probes regardless of their types, some of the columns will be "not applicable" to some of the probes (like, say, the Semaphore column only makes sense for SystemTap probes). This patch makes `info probes' fill these slots with "n/a" marks (currently it breaks the table) and not include headers for which no actual probe has been found in the list of defined probes. This patch also adds support for a new generic column "Type", that displays the type of each probe. SystemTap probes identify themselves as "stap" probes. gdb/ChangeLog: 2015-02-17 Jose E. Marchesi <jose.marchesi@oracle.com> * probe.c (print_ui_out_not_applicables): New function. (exists_probe_with_pops): Likewise. (info_probes_for_ops): Do not include column headers for probe types for which no probe has been actually found on any object. Also invoke `print_ui_out_not_applicables' in order to match the column rows with the header when probes of several types are listed. Print the "Type" column. * probe.h (probe_ops): Added a new probe operation `type_name'. * stap-probe.c (stap_probe_ops): Add `stap_type_name'. (stap_type_name): New function.
next reply other threads:[~2015-02-17 17:52 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-17 18:00 sergiodj [this message] 2015-02-17 18:11 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj 2015-02-17 19:12 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj 2015-02-17 19:52 ` Failures on Fedora-i686, " sergiodj 2015-02-17 20:28 ` Failures on Fedora-x86_64-m32, " sergiodj 2015-02-17 20:35 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj 2015-02-17 20:38 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj 2015-02-17 21:28 ` Failures on Fedora-x86_64-m64, " sergiodj 2015-02-17 21:35 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj 2015-02-17 22:40 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj 2015-02-17 23:21 ` Failures on Debian-i686-cc-with-index, " sergiodj 2015-02-17 23:38 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj 2015-02-18 0:22 ` Failures on Debian-i686-native-gdbserver, " sergiodj 2015-02-18 1:22 ` Failures on Debian-x86_64-native-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=6f9b84910f8cabf565598f499258bbea51cc06d4@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).