From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "姜涛 Tao(AD)" <tao.jiang@jiduauto.com>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] lttng-analysis error
Date: Tue, 31 Oct 2023 15:36:15 -0400 [thread overview]
Message-ID: <abf9f8b8-059c-437f-a8d3-aa796d9564d2@efficios.com> (raw)
In-Reply-To: <ZQ0PR01MB1062ED24B7D2F6A14F06A92197A0A@ZQ0PR01MB1062.CHNPR01.prod.partner.outlook.cn>
Hi Tao,
based on a quick test I performed, there may be a work-around that will
work for you.
The issue that I see is that at least the
`lttng_statedump_file_descriptor` events no longer have a pid field
which the older lttng-analyses code assumes is present.
To find this out
When running the manual recording steps, could you add the following
command before running `lttng start`:
```
lttng add-context --kernel --type=pid
```
To pinpoint the source of the error, I used the `--debug` parameter for
`lttng-analyses` as follows:
```
# lttng-schedtop --debug
lttng-traces/lttng-analysis-27010-20231031-182735/
Checking the trace for lost events...
Traceback (most recent call last):
] ETA: --:--:--
File
"/usr/local/lib/python3.7/dist-packages/lttnganalyses/cli/command.py",
line 73, in _run_step
fn()
File
"/usr/local/lib/python3.7/dist-packages/lttnganalyses/cli/command.py",
line 365, in _run_analysis
self._automaton.process_event(event)
File
"/usr/local/lib/python3.7/dist-packages/lttnganalyses/linuxautomaton/automaton.py",
line 81, in process_event
sp.process_event(ev)
File
"/usr/local/lib/python3.7/dist-packages/lttnganalyses/linuxautomaton/sp.py",
line 33, in process_event
self._cbs[name](ev)
File
"/usr/local/lib/python3.7/dist-packages/lttnganalyses/linuxautomaton/statedump.py",
line 91, in _process_lttng_statedump_file_descriptor
pid = event['pid']
File
"/usr/local/lib/python3.7/dist-packages/babeltrace/babeltrace.py", line
912, in __getitem__
raise KeyError(field_name)
KeyError: 'pid'
Error: Cannot run analysis: 'pid'
```
thanks,
kienan
On 2023-10-31 07:44, 姜涛 Tao(AD) via lttng-dev wrote:
> Hi everyone, I use lttng-analysis tools to parse the trace files but get
> error as below:
>
> I try two methods to catch the trace data: “automatic” using
> lttng-analysis-record and “manual” using lttng
> create/enable-event/start/stop/destroy, but always get the errors when
> using lttng-analysis tools(0.6.0 and 0.6.1 version).
>
> I load the lttng modules(2.12.14 version) successfully:
>
> 文本 描述已自动生成
>
> The environment is as below: Ubuntu20.04 aarch64, kernel version:
> 5.10.120 rt patch.
>
> Any help will be appreciated! Thanks!
>
> 免责声明:本邮件所包含信息发给指定个人或机构,邮件可能包含保密或专属信
> 息。未经接收者许可,不得阅读、转发或传播邮件内容,或根据邮件内容采取任何
> 相关行动。如果错误地收到了此邮件,请与收件人联系并自行删除邮件内容。
> Disclaimer:The information transmitted is intended only for the person
> or entity to which it is addressed and may contain confidential and/or
> privileged material. Any review, retransmission, dissemination or other
> use of, or taking of any action in reliance upon, this information by
> persons or entities other than the intended recipient is prohibited. If
> you received this in error , please contact the sender and delete the
> material from any computer.
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
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:[~2023-10-31 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 11:44 [lttng-dev] lttng-analysis error 姜涛 Tao(AD) via lttng-dev
2023-10-31 19:36 ` Kienan Stewart via lttng-dev [this message]
[not found] ` <ZQ0PR01MB1062F47CF4B19FF30D81FAFD97A7A@ZQ0PR01MB1062.CHNPR01.prod.partner.outlook.cn>
2023-11-01 15:11 ` [lttng-dev] 答复: " Kienan Stewart 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=abf9f8b8-059c-437f-a8d3-aa796d9564d2@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.com \
--cc=tao.jiang@jiduauto.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).