| Server IP : 185.124.137.52 / Your IP : 216.73.216.71 Web Server : LiteSpeed System : Linux id-dci-web1986.main-hosting.eu 5.14.0-611.26.1.el9_7.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jan 29 05:24:47 EST 2026 x86_64 User : u686484674 ( 686484674) PHP Version : 8.0.30 Disable Function : system, exec, shell_exec, passthru, mysql_list_dbs, ini_alter, dl, symlink, link, chgrp, leak, popen, apache_child_terminate, virtual, mb_send_mail MySQL : OFF | cURL : ON | WGET : ON | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /./opt/golang/1.22.0/src/internal/trace/v2/testdata/ |
Upload File : |
# Trace test data ## Trace golden tests Trace tests can be generated by running ``` go generate . ``` with the relevant toolchain in this directory. This will put the tests into a `tests` directory where the trace reader tests will find them. A subset of tests can be regenerated by specifying a regexp pattern for the names of tests to generate in the `GOTRACETEST` environment variable. Test names are defined as the name of the `.go` file that generates the trace, but with the `.go` extension removed. ## Trace test programs The trace test programs in the `testprog` directory generate traces to stdout. Otherwise they're just normal programs. ## Trace debug commands The `cmd` directory contains helpful tools for debugging traces. * `gotraceraw` parses traces without validation. It can produce a text version of the trace wire format, or convert the text format back into bytes. * `gotracevalidate` parses traces and validates them. It performs more rigorous checks than the parser does on its own, which helps for debugging the parser as well. In fact, it performs the exact same checks that the tests do.