X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=README.markdown;h=f69991485bb66150acdef9fe36f3f13341f41183;hb=778420084d839635d672dab1d65368618592bd5d;hp=2d37898f820bf88c2b42e68820f8abddee3928b1;hpb=5785b4f8e6bebc89c85316253ab4f763065a0264;p=apitrace

diff --git a/README.markdown b/README.markdown
index 2d37898..f699914 100644
--- a/README.markdown
+++ b/README.markdown
@@ -145,10 +145,6 @@ If you are an application developer, you can avoid this either by linking with
 See the `ld.so` man page for more information about `LD_PRELOAD` and
 `LD_LIBRARY_PATH` environment flags.
 
-To trace the application inside gdb, invoke gdb as:
-
-    gdb --ex 'set exec-wrapper env LD_PRELOAD=/path/to/glxtrace.so' --args /path/to/application
-
 ### Android ###
 
 To trace standalone native OpenGL ES applications, use
@@ -294,14 +290,20 @@ You can make a video of the output with gstreamer by doing
 Trimming a trace
 ----------------
 
-You can make a smaller trace by doing:
+You can truncate a trace by doing:
 
-    apitrace trim --callset 100-1000 -o trimed.trace applicated.trace
+    apitrace trim --exact --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 a plaintext file, as described in the 'Call sets'
 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
+
 
 Profiling a trace
 -----------------