From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-44086-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 4559 invoked by alias); 4 Feb 2015 16:21:27 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 4544 invoked by uid 89); 4 Feb 2015 16:21:26 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,LIKELY_SPAM_BODY,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-qc0-f169.google.com
Received: from mail-qc0-f169.google.com (HELO mail-qc0-f169.google.com) (209.85.216.169) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 04 Feb 2015 16:21:25 +0000
Received: by mail-qc0-f169.google.com with SMTP id b13so2034029qcw.0        for <gdb@sourceware.org>; Wed, 04 Feb 2015 08:21:23 -0800 (PST)
X-Received: by 10.229.204.74 with SMTP id fl10mr22712020qcb.24.1423066883184; Wed, 04 Feb 2015 08:21:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.39.209 with HTTP; Wed, 4 Feb 2015 08:21:02 -0800 (PST)
In-Reply-To: <1414504151-31155-9-git-send-email-jose.marchesi@oracle.com>
References: <1414504151-31155-1-git-send-email-jose.marchesi@oracle.com> <1414504151-31155-9-git-send-email-jose.marchesi@oracle.com>
From: Ed Maste <emaste@freebsd.org>
Date: Wed, 04 Feb 2015 16:21:00 -0000
Message-ID: <CAPyFy2AAS8k8pY2Z-n8qWbOJhFn2kxsDdTrGtBc=yvVS9MeFbg@mail.gmail.com>
Subject: Re: [PATCH V3 8/9] Documentation for DTrace USDT probes.
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb@sourceware.org
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2015-02/txt/msg00008.txt.bz2

On 28 October 2014 at 09:49, Jose E. Marchesi <jose.marchesi@oracle.com> wrote:
> +Some @code{SystemTap} probes have an associated semaphore variable;
> +for instance, this happens automatically if you defined your probe
> +using a DTrace-style @file{.d} file.  If your probe has a semaphore,
> +@value{GDBN} will automatically enable it when you specify a
> +breakpoint using the @samp{-probe-stap} notation.  But, if you put a
> +breakpoint at a probe's location by some other method (e.g.,
> +@code{break file:line}), then @value{GDBN} will not automatically set
> +the semaphore.  @code{DTrace} probes do not support semaphores.

This seems confusing to me now that there is additional DTrace context
in this paragraph: something unsupported by DTrace happens
automatically when using a DTrace-style .d file. Would something like
"a standalone probe definition file" be better than "DTrace-style"?