From: Yuan Bin via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] Nano clock value overflows the signed 64-bit integer range on the babeltrace2 client side when per-process per-user trace file were transfer using lttng live protocol
Date: Fri, 24 Mar 2023 19:34:43 +0800 [thread overview]
Message-ID: <CAL_9pdT9tDgj3e2YNsWFn6YkOAVWbcoUKXaE+YveJiFrOeu+NQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 780 bytes --]
I launched a program producing traces to the lttng consumerd and lttng
relayd, also launching a babeltrace command as lttng live consumer to show
the tracing real-timely.
It works well when the channel is set to per user mode. But when it is
changed to per process per user without no other changes, the babeltrace2
client crashing showing a overflow error:
The last error message of babeltrace2 exception stack shows :
"Cannot convert cycle to nanoseconds from origin for given clock class:
value overflows the signed 64-bit integer range: cc-addr=****,
cc-name="monotonic", cc-freq=1000000000, ....."
What's the difference resulting this crash ? How to solve it since the
perprocess per user mode is perfered for me.
version info:
babeltrace2: 2.0.4
lttng comands: 2.12.12
[-- Attachment #1.2: Type: text/html, Size: 1282 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
reply other threads:[~2023-03-24 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAL_9pdT9tDgj3e2YNsWFn6YkOAVWbcoUKXaE+YveJiFrOeu+NQ@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=elf.ggle@gmail.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