From d9809aa93ce4bdeb57f1ab81decea4b54cf20026 Mon Sep 17 00:00:00 2001 From: Jose Fonseca Date: Thu, 6 Aug 2015 12:19:25 +0100 Subject: cli: Split automatic trimming into its own command. Automatic trimming hasn't graduated its experimental status: it still has several limitations and bugs, and hasn't been maintained pretty much since it was merged. Keeping automatic and exact trimming together ends up confusing users, and also makes the exact trimming unnecessarily slow and complex (2 passes over the trace where 1 pass would suffice.) I also hope one day to rewrite auto-trimming (autotrim-v2 branch.) --- docs/USAGE.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/USAGE.markdown b/docs/USAGE.markdown index d90dbe8c..eb4a8729 100644 --- a/docs/USAGE.markdown +++ b/docs/USAGE.markdown @@ -363,7 +363,7 @@ You can make a video of the output with gstreamer by doing You can truncate a trace by doing: - apitrace trim --exact --calls 0-12345 -o trimed.trace application.trace + apitrace trim --calls 0-12345 -o trimed.trace application.trace If you need precise control over which calls to trim you can specify the individual call numbers in a plain text file, as described in the 'Call sets' @@ -372,8 +372,8 @@ section above. There is also experimental support for automatically trimming the calls necessary for a given frame or call: - apitrace trim --auto --calls=12345 -o trimed.trace application.trace - apitrace trim --auto --frames=12345 -o trimed.trace application.trace + apitrace trim-auto --calls=12345 -o trimed.trace application.trace + apitrace trim-auto --frames=12345 -o trimed.trace application.trace ## Profiling a trace ## -- cgit v1.2.3