From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: linux-trace-users <linux-trace-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: lttng-trace: a new strace-alike LTTng command
Date: Thu, 18 Feb 2021 17:14:24 -0500 (EST) [thread overview]
Message-ID: <2137653784.27421.1613686464160.JavaMail.zimbra@efficios.com> (raw)
Hi there!
I just pushed a new command line tool named `lttng-trace`, which allows tracing a
specific command and its sub-processes using the LTTng system call tracer. It focuses
on simplicity. It can be found here:
Git website: http://git.lttng.org/?p=lttng-trace.git
Clone with:
git clone https://git.lttng.org/lttng-trace.git
For instance, tracing the command "date" is as simple as:
lttng-trace date
The tracing session can be optionally configured by using the usual lttng control
interfaces after this message appears:
[lttng-trace] Tracing session `date-20210218-170545` created. It can be customized using the `lttng` command.
[lttng-trace] Press <ENTER> key when ready to run the child process.
After execution of the command, the following message details how to view the trace:
[lttng-trace] Sub-process hierarchy traced successfully. View trace with `babeltrace2 /tmp/lttng-trace/date-20210218-170906`
See `lttng-trace --help` for more options.
This new command is in early alpha stage. Feedback is welcome! For instance, we are wondering whether
the default behavior should just be tracing system calls, or if some level of user-space tracing should
be enabled by default as well. Or if some new options should enable "typical" usage scenarios.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Cc: linux-trace-users <linux-trace-users@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [lttng-dev] lttng-trace: a new strace-alike LTTng command
Date: Thu, 18 Feb 2021 17:14:24 -0500 (EST) [thread overview]
Message-ID: <2137653784.27421.1613686464160.JavaMail.zimbra@efficios.com> (raw)
Hi there!
I just pushed a new command line tool named `lttng-trace`, which allows tracing a
specific command and its sub-processes using the LTTng system call tracer. It focuses
on simplicity. It can be found here:
Git website: http://git.lttng.org/?p=lttng-trace.git
Clone with:
git clone https://git.lttng.org/lttng-trace.git
For instance, tracing the command "date" is as simple as:
lttng-trace date
The tracing session can be optionally configured by using the usual lttng control
interfaces after this message appears:
[lttng-trace] Tracing session `date-20210218-170545` created. It can be customized using the `lttng` command.
[lttng-trace] Press <ENTER> key when ready to run the child process.
After execution of the command, the following message details how to view the trace:
[lttng-trace] Sub-process hierarchy traced successfully. View trace with `babeltrace2 /tmp/lttng-trace/date-20210218-170906`
See `lttng-trace --help` for more options.
This new command is in early alpha stage. Feedback is welcome! For instance, we are wondering whether
the default behavior should just be tracing system calls, or if some level of user-space tracing should
be enabled by default as well. Or if some new options should enable "typical" usage scenarios.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2021-02-18 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 22:14 Mathieu Desnoyers [this message]
2021-02-18 22:14 ` [lttng-dev] lttng-trace: a new strace-alike LTTng command 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=2137653784.27421.1613686464160.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.