From: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
To: linux-trace-users@vger.kernel.org,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: [ANNOUNCE] trace-cruncher 0.3.0 (beta)
Date: Tue, 22 Nov 2022 15:25:43 +0200 [thread overview]
Message-ID: <CAPpZLN7EMZNFL4dFkCSxGVj8SLy=+qVfoOqqRdkNw2CdnfFHPQ@mail.gmail.com> (raw)
Notable changes in the new trace-cruncher release:
- Introduced initial support for ftrace uprobes.
- New flexible wait() API, useful to wait for various conditions during
the trace.
- Improvements that allow trace-cruncher to be used within a container
context.
- Introduced github development workflow, additional to the current
mailing list approach. Both development workflows are supported,
patches can be sent to linux-trace-devel@vger.kernel.org mailing
list or as pull requests to github.com/vmware/trace-cruncher
- A lot of fixes, documentation and test updates.
See the changelog for a complete list.
https://github.com/vmware/trace-cruncher/releases/tag/tracecruncher-v0.3.0
--
Tzvetomir (Ceco) Stoyanov
VMware Open Source Technology Center
reply other threads:[~2022-11-22 13:26 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='CAPpZLN7EMZNFL4dFkCSxGVj8SLy=+qVfoOqqRdkNw2CdnfFHPQ@mail.gmail.com' \
--to=tz.stoyanov@gmail.com \
--cc=linux-trace-devel@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).