lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Shubham Kulkarni via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Suspected Bug in lttng-tools
Date: Tue, 27 Dec 2022 17:26:44 +0530	[thread overview]
Message-ID: <CAGWKocZ9E=oMDD09sm9zstKyt7yOxSW2pk0aDxeuxD0tSCb9DQ@mail.gmail.com> (raw)
In-Reply-To: <CAGWKocYTK=vVyh3DjHHoKWj_Fua_Qjc+7ruG1R6d=Y2ki7uraQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2813 bytes --]

Hi,

Please ignore the previous mail from me saying there might be a bug in
lttng-tools. After some analysis, I found this is expected functionality as
per the commit https://github.com/lttng/lttng-tools/commit/cb034ca.
It's NOT A BUG.

Thanks,
Shubham


On Mon, Dec 26, 2022 at 3:52 PM Shubham Kulkarni <shubhambkul16@gmail.com>
wrote:

> Hi,
>
> I am entirely new to the lttng-tools and frankly not aware of anything.
> But, one of our company's customer reported this issue, so I tried
> reproducing. I was able to reproduce it with the version of lttng-tool
> (2.12.4 - (Ta) Meilleure) installed on my Ubuntu 16.04 (
> https://lttng.org/docs/v2.12/#doc-ubuntu-ppa).
>
> Issue is, if I try to snapshot a session with an output filename
> containing a ".", it fails. Steps I followed are given below :
>
> *"*
> root@MVIN00032:~# lttng create flightrecorder --snapshot
> Snapshot session flightrecorder created.
> Default snapshot output set to
> /home/shubham/lttng-traces/flightrecorder-20221223-153147
> Every channel enabled for this session will be set to mmap output and
> default to overwrite mode.
>
> root@MVIN00032:~# lttng enable-event -k -a
> All Kernel events are enabled in channel channel0
>
> root@MVIN00032:~# lttng start
> Tracing started for session flightrecorder
>
> root@MVIN00032:~# lttng -vvv snapshot record -s flightrecorder -n
> *record.dump*
> DEBUG1 - 15:32:15.173476719 [7159/7159]: LSM cmd type : 28 (in
> send_session_msg() at lttng-ctl.c:128)
> *Error: Create directory failed*
> DEBUG1 - 15:32:15.197542565 [7159/7159]: Clean exit (in clean_exit() at
> lttng.c:152)
>
> root@MVIN00032:~# lttng -vvv snapshot record -s flightrecorder -n
> *record_dump*
> DEBUG1 - 15:32:24.013450964 [7442/7442]: LSM cmd type : 28 (in
> send_session_msg() at lttng-ctl.c:128)
> *Snapshot recorded successfully for session flightrecorder*
>
> root@MVIN00032:~# lttng stop
> Waiting for data availability
> Tracing stopped for session flightrecorder
>
> root@MVIN00032:~# lttng destroy
> Session flightrecorder destroyed *"*
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> I tried the same with lttng-tools v2.9.5 (as one of my company's product
> uses this version) under runqemu session, which worked fine for
> 'record.dump' & with lttng-tools v2.11.5 (another product uses this
> version) failed with the same error. So, maybe in between these versions an
> issue was introduced.
>
> I am not sure whether this is the correct location to send this mail, but
> I didn't find any solution on the Internet and I am not aware of lttng at
> all. I was able to reproduce the issue with help from the internet, so
> thought to report it via this mailing list.
>
> Thanks,
> Shubham
>

[-- Attachment #1.2: Type: text/html, Size: 3579 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:[~2022-12-27 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 10:22 [lttng-dev] Suspected Bug in lttng-tools Shubham Kulkarni via lttng-dev
2022-12-27 11:56 ` Shubham Kulkarni via lttng-dev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-23 13:24 Shubham Kulkarni 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='CAGWKocZ9E=oMDD09sm9zstKyt7yOxSW2pk0aDxeuxD0tSCb9DQ@mail.gmail.com' \
    --to=lttng-dev@lists.lttng.org \
    --cc=shubhambkul16@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;
as well as URLs for NNTP newsgroup(s).