From: Namhyung Kim <namhyung@gmail.com>
To: uftrace@googlegroups.com, linux-trace-devel@vger.kernel.org
Subject: [ANNOUNCE] uftrace v0.19 is released
Date: Sun, 1 Mar 2026 22:19:49 -0800 [thread overview]
Message-ID: <20260302061950.7293-1-namhyung@gmail.com> (raw)
Hello,
I'm excited to announce that uftrace v0.19 is just released!
This is a small release with bug fixes/updates and some new features.
You can get it from the below link:
https://github.com/namhyung/uftrace/releases/tag/v0.19
uftrace dump command that generates chrome trace output format supports
adding source file and line number information.
$ uftrace dump --chrome --srcline
Also it now shows the timestamp as realtime with UTC offsets so that it
can correlate trace output with external events easily.
And it has a new script to show function execution time percentiles
(P90, P95, P99).
$ uftrace script -S scripts/func-percentile.py $FUNCNAME
As more useful scripts are added, we'll need to think about how to
deploy them.
And there are a couple of important bug fixes.
PLT functions generated by mold linker have different code patterns and
cause uftrace crash. Now it's fixed and trace them correctly.
And it checks RISC-V 64 CPUs properly in the hashmap code.
And there are more bug fixes and improvements. Thank you all for
making uftrace more useful, efficient and portable!
Namhyung
reply other threads:[~2026-03-02 6:19 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=20260302061950.7293-1-namhyung@gmail.com \
--to=namhyung@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=uftrace@googlegroups.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