From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84765C07E99 for ; Fri, 9 Jul 2021 13:54:58 +0000 (UTC) Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D3DE761208 for ; Fri, 9 Jul 2021 13:54:51 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D3DE761208 Authentication-Results: mail.kernel.org; dmarc=pass (p=none dis=none) header.from=lists.lttng.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lttng-dev-bounces@lists.lttng.org Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4GLvmS24Dnz109K; Fri, 9 Jul 2021 09:54:48 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1625838888; bh=0BT5jG+1tdspB6TMK/A+U+vZg5+xUPSQkc8xEHamcMA=; h=Date:To:Cc:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=BVrWMZ5w1XEnXx0wwkfidDEtAEVC0CYdpdRd7RwsOoGzKhZkBgQt5qPOWcXTaDpxG eAxOhNzt/H8G2sjqf+gvVSGhh7Xh7Z8/yVTomM6D3mNKIOK5AWIA2Cm70Mn4VRZ23j IMOKTrbJidnW8lroSDZjw/dqWgBJDoDmZqQzWpGuVqhqfD9hK20Yx/pyjp6W8C6yvF bJnjvPVLzYrGU/8mV4ipDGfGFZg1X370GXB7K3zw/85hDEsZeVvC+DmRPL+3KTGQVq Z8oO6Xet213yHSY5Wf07SOiPBqF20rjh3PlWj/t89+3KPXM3g0JAkbrODzTDJHV1pz dC1g3CUqlPEnA== Received: from mail.efficios.com (mail.efficios.com [167.114.26.124]) by lists.lttng.org (Postfix) with ESMTPS id 4GLvmQ18dqzynh for ; Fri, 9 Jul 2021 09:54:45 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id 9E767356217 for ; Fri, 9 Jul 2021 09:54:39 -0400 (EDT) Received: from mail.efficios.com ([127.0.0.1]) by localhost (mail03.efficios.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id igwON3Q_8l9s; Fri, 9 Jul 2021 09:54:35 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id 83ED0356120; Fri, 9 Jul 2021 09:54:35 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com 83ED0356120 X-Virus-Scanned: amavisd-new at efficios.com Received: from mail.efficios.com ([127.0.0.1]) by localhost (mail03.efficios.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wG6BSgoCbVDK; Fri, 9 Jul 2021 09:54:35 -0400 (EDT) Received: from mail03.efficios.com (mail03.efficios.com [167.114.26.124]) by mail.efficios.com (Postfix) with ESMTP id 752A835611F; Fri, 9 Jul 2021 09:54:35 -0400 (EDT) Date: Fri, 9 Jul 2021 09:54:35 -0400 (EDT) To: Evan Galea Cc: lttng-dev Message-ID: <482770069.11167.1625838875359.JavaMail.zimbra@efficios.com> In-Reply-To: References: MIME-Version: 1.0 X-Originating-IP: [167.114.26.124] X-Mailer: Zimbra 8.8.15_GA_4059 (ZimbraWebClient - FF89 (Linux)/8.8.15_GA_4059) Thread-Topic: unable to add callstack-user context Thread-Index: bXYt4q9lOk763sg3WhWl7pl6z9aQ4A== Subject: Re: [lttng-dev] unable to add callstack-user context X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Mathieu Desnoyers via lttng-dev Reply-To: Mathieu Desnoyers Content-Type: multipart/mixed; boundary="===============3351437464262535608==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============3351437464262535608== Content-Type: multipart/alternative; boundary="=_89a983c4-4b9e-4d49-9361-0d8a51d67f4b" --=_89a983c4-4b9e-4d49-9361-0d8a51d67f4b Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit ----- On Jul 9, 2021, at 4:30 AM, lttng-dev wrote: > Hi there, I'm a little new to lttng and tracing in general. I am using a Java > Userspace agent, which is working well, but I am having trouble adding > callstack context to my tracing channels. I'm not sure if it's relevant but > running 'lttng add-context --list" shows callstack-user in the list. It's not surprising, because the callstack-user context is specific to the kernel tracer. > the commands I input are: > lttng create > lttng enable-channel --userspace mychannel > lttng enable-event --userspace --all --channel mychannel > lttng add-context --userspace --channel mychannel --type callstack-user > >Error: callstack-user: UST invalid context This is expected. > When I run the following command instead: > lttng add-context --userspace --channel mychannel --type vpid > I am able to get it to work and I see vpid appear in my traces. Are there any > other things I need to set up first to be able to use it? > also, are there any commands that can list the per-domain contexts available? Not currently, though I think it would make sense to make "lttng add-context --list" allow a tracing domain (e.g. --kernel/--userspace) to be specified as a future improvement. Some information about this is available in the lttng-add-context(1) man page, but the fact that the kernel and user callstack contexts are only supported by the kernel tracer don't seem to be mentioned. Thanks, Mathieu > _______________________________________________ > lttng-dev mailing list > lttng-dev@lists.lttng.org > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com --=_89a983c4-4b9e-4d49-9361-0d8a51d67f4b Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
----- On Jul 9, 2021, at 4:30 AM, lttng-dev <lttng-dev@lists.lttng.o= rg> wrote:
Hi there, I'm a little new to lttng and tracing in general. = I am using a Java Userspace agent, which is working well, but I am having t= rouble adding callstack context to my tracing channels. I'm not sure if it'= s relevant but running 'lttng add-context --list" shows callstack-user in t= he list.

It's not surpris= ing, because the callstack-user context is specific to the kernel tracer.


the commands I input are:

lttng create =
lttng enable-channel --userspace mychannel
lttng e= nable-event --userspace --all --channel mychannel
lttng add-c= ontext --userspace --channel mychannel --type callstack-user
>= Error: callstack-user: UST invalid context

This is expected.


When I run the follow= ing command instead:
lttng add-context --userspace --channel = mychannel --type vpid

I am able to get it to work and I see v= pid appear in my traces. Are there any other things I need to set up first = to be able to use it?

also, are there any commands that can l= ist the per-domain contexts available?
<= br>
Not currently, though I think it would make sense to make "lt= tng add-context --list" allow a tracing domain
(e.g. --kernel/--userspace) to be specified as a future improvement.=

Som= e information about this is available in the lttng-add-context(1) man page,= but the fact that the
kernel and user c= allstack contexts are only supported by the kernel tracer don't seem to be = mentioned.

Thanks,

=
Mathieu



_______________________________________________
lttng-dev mailing li= st
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/= listinfo/lttng-dev

--
Mathieu Desnoyers
EfficiOS Inc.
http= ://www.efficios.com
--=_89a983c4-4b9e-4d49-9361-0d8a51d67f4b-- --===============3351437464262535608== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============3351437464262535608==--