linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
	"linux-trace-users@vger.kernel.org" 
	<linux-trace-users@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Subject: [ANNOUNCE] trace-cmd v3.2 is released
Date: Wed, 7 Jun 2023 19:25:41 -0400	[thread overview]
Message-ID: <20230607192541.25780fef@gandalf.local.home> (raw)


https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/tag/?h=trace-cmd-v3.2

trace-cmd: Version 3.2

Features and user visible updates since 3.1.6

 - Open coded the execvp() to not start tracing until the actual path of the
   executable is found. The trace no longer contains the failed execs of
   execvp() trying various paths.

 - Add global filter support to trace-cmd read. If the -F filter is placed
   before any -i file, it will be applied to all files. Otherwise the -F filter
   will only be applied to the last file specified.

 - Added new "attach" command that can take a trace.dat file created from the host
   at the same time a trace.dat file was created on one of its guests, and be
   able to set the meta data to hook them together like if it was done via
   trace-cmd agent. This is useful for boot time tracing.

Fixes since 3.1.6

 - Fix the way filters were applied to trace-cmd report with multiple trace.dat
   files.

 - Fixed trace-cmd extract to not extract the top level buffer unless
   specifically asked to. That is, "trace-cmd extract -B foo" will only extract
   the data from foo and not the top level buffer.

 - Fixed record and extract to not destroy specified instances if they were not
   created by the record or extract.

 - Add memory (valgrind) testing to utest.

 - Add meson build support (although it's not the default yet).

https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/

Enjoy!

-- Steve

                 reply	other threads:[~2023-06-07 23:25 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=20230607192541.25780fef@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux-trace-users@vger.kernel.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 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).