From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27496 invoked by alias); 17 Oct 2014 00:07:09 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 27405 invoked by uid 89); 17 Oct 2014 00:07:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,LIKELY_SPAM_BODY,RCVD_IN_DNSWL_LOW,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mail-vc0-f179.google.com Received: from mail-vc0-f179.google.com (HELO mail-vc0-f179.google.com) (209.85.220.179) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 17 Oct 2014 00:07:07 +0000 Received: by mail-vc0-f179.google.com with SMTP id im17so3561854vcb.38 for ; Thu, 16 Oct 2014 17:07:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mQZjMN7MbLHM+XptCTV3vDYfArDV+NcmmV75IpHy9Pc=; b=iUzjfZOWVQpMIYmm1xw8+NF20Z1av/qlGuBNYcXBTnu8K7GlJVzqpR7Yi8sNECOB3/ NazjVcFzAyGQ9Ulhmbx5LMEumLrJFM4Jdj0d4SagRusTxFV1Lrsuw76tizm/I+57IFqb 8frYsKNo+55TEEEspzTwlzIXegSzuPcyV4tolIlN9YNm98Wp5cCPtM1ICBsY8R4sCE7O hACYbs405q6R3m+/svWQ2gMeIpA7SZOqh4t+la5bDnTXscsoy1PQsLqMco4Si1n/Gphm Ifu9DMYiqNxE5jlgUO1eairChWEVVyejvUArzla8JdLCZ1hiEGdbynrXg4aSJ4OV92hK 0jiA== X-Gm-Message-State: ALoCoQnqlhhx3292NJBCrAduDFPnYAlxVKAa/sANTOm9foMyO4tnZRgfcPB6VO25KpQ/XGK4CuTD MIME-Version: 1.0 X-Received: by 10.221.51.8 with SMTP id vg8mr4579148vcb.0.1413504425545; Thu, 16 Oct 2014 17:07:05 -0700 (PDT) Received: by 10.52.161.132 with HTTP; Thu, 16 Oct 2014 17:07:05 -0700 (PDT) In-Reply-To: <8761fmqxul.fsf@redhat.com> References: <1412961772-16249-1-git-send-email-jose.marchesi@oracle.com> <1412961772-16249-4-git-send-email-jose.marchesi@oracle.com> <21560.22449.803178.90104@ruffy2.mtv.corp.google.com> <878uknun2f.fsf@oracle.com> <8761fmqxul.fsf@redhat.com> Date: Fri, 17 Oct 2014 00:07:00 -0000 Message-ID: Subject: Re: [PATCH V2 3/9] New commands `enable probe' and `disable probe'. From: Doug Evans To: Sergio Durigan Junior Cc: "Jose E. Marchesi" , gdb-patches Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2014-10/txt/msg00447.txt.bz2 On Tue, Oct 14, 2014 at 12:01 PM, Sergio Durigan Junior wrote: > On Monday, October 13 2014, Doug Evans wrote: > >> On Fri, Oct 10, 2014 at 11:39 PM, Jose E. Marchesi >> wrote: >>> >>> Hi Doug. >>> >>> Would it be useful to have "info probes" show >>> the enable/disable state of each probe? >>> Or at least know which ones have been disabled. >>> >>> Right, `info probes' actually tells you the "Enabled" status of the >>> probes, provided there is at least one dtrace probe in the executable. >>> For example: >>> >>> (gdb) info probes >>> Provider Name Where Semaphore Enabled Object >>> demo am-main 0x0000000000400c96 n/a /home/jemarch/oracle/usdt/demo >>> demo another 0x0000000000400c8b n/a always /home/jemarch/oracle/usdt/demo >>> demo progress-counter 0x0000000000400c81 n/a no /home/jemarch/oracle/usdt/demo >> >> Thanks. I couldn't find it, where should I look? > > This is on patch 1/9. Thanks. I found the details of the "Enabled" column in 5/9.