From: "zhenyu.ren via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev" <lttng-dev@lists.lttng.org>,
"mathieu.desnoyers" <mathieu.desnoyers@efficios.com>
Subject: [lttng-dev] 回复： 回复： some tracepoints not exist in metadata?
Date: Wed, 01 Jul 2020 11:56:38 +0800 [thread overview]
Message-ID: <65af8a29-4fd7-454c-a060-8f06cb7bc931.zhenyu.ren@aliyun.com> (raw)
Message-ID: <20200701035638.UxZIPL2SrqokVfq2XqPUFeZSFAeUy74AjywWAC1IayE@z> (raw)
In-Reply-To: <49dab706-ab7e-4156-9163-b8d9105b173d.zhenyu.ren@aliyun.com>
[-- Attachment #1.1: Type: text/plain, Size: 1637 bytes --]
Ah, I have to say that I use the wildcard in tracepoint name when enable-event to the channel, i.e. ./lttng enable-event -u system_event* -c channel0 -s misc_data. Of course, there are the other tracepoints with wildcard succeed in registring.
------------------------------------------------------------------
发件人：zhenyu.ren via lttng-dev <lttng-dev@lists.lttng.org>
发送时间：2020年7月1日(星期三) 11:44
收件人：lttng-dev <lttng-dev@lists.lttng.org>; mathieu.desnoyers <mathieu.desnoyers@efficios.com>
主 题：[lttng-dev] 回复： some tracepoints not exist in metadata?
I'd like to add that both "lttng list -u" and "lttng list $session_name" can get those tracepoints' names...
------------------------------------------------------------------
发件人：zhenyu.ren via lttng-dev <lttng-dev@lists.lttng.org>
发送时间：2020年7月1日(星期三) 11:05
收件人：lttng-dev <lttng-dev@lists.lttng.org>; mathieu.desnoyers <mathieu.desnoyers@efficios.com>
主 题：[lttng-dev] some tracepoints not exist in metadata?
Hi,
I find sometimes there are some tracepoints not exist in metadata file(but they are in the list of lttng list -u) and the end result is they can NOT be logged. I can not always reproduce it. It bothered me for 2 days.
The lttng version is 2.7, I know it is not the latest version but there are some reasons I can't update it. So, is this a known bug? If yes, It will be very appreciated if you can give me any advice about the bug info(I can cherry pick the correspond fix). Otherwise, maybe I have to give up my favoriate Lttng....
Thank you in advance!
zhenyu.ren
[-- Attachment #1.2: Type: text/html, Size: 4576 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-07-01 3:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 2:48 some tracepoints not exist in metadata? zhenyu.ren via lttng-dev
2020-07-01 2:48 ` [lttng-dev] " zhenyu.ren via lttng-dev
2020-07-01 3:43 ` 回复： " zhenyu.ren via lttng-dev
2020-07-01 3:43 ` [lttng-dev] " zhenyu.ren via lttng-dev
2020-07-01 3:56 ` zhenyu.ren via lttng-dev [this message]
2020-07-01 3:56 ` [lttng-dev] 回复： " zhenyu.ren via lttng-dev
2020-07-01 12:07 ` Mathieu Desnoyers via lttng-dev
2020-07-01 12:07 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
2020-07-02 0:38 ` 回复：回复： " zhenyu.ren via lttng-dev
2020-07-02 0:38 ` [lttng-dev] " zhenyu.ren via lttng-dev
2020-07-02 12:45 ` Jonathan Rajotte-Julien via lttng-dev
2020-07-02 12:45 ` [lttng-dev] " Jonathan Rajotte-Julien via lttng-dev
2020-07-02 14:03 ` Mathieu Desnoyers via lttng-dev
2020-07-02 14:03 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
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=65af8a29-4fd7-454c-a060-8f06cb7bc931.zhenyu.ren@aliyun.com \
--to=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=zhenyu.ren@aliyun.com \
/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: link
Be 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 NNTP newsgroup(s).