diff options
| author | Ludovic Henry <luhenry@microsoft.com> | 2017-09-25 19:27:47 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-25 19:27:47 +0300 |
| commit | 5b681a16bd7aaf579f6b4a32eed36ee05bd4f562 (patch) | |
| tree | 102fe6a29761339d5888e03dfae93150fb2f4376 /man/mprof-report.1 | |
| parent | fc6f7e7921bc0367ad3d042ce5b8fe2d6dfe54e4 (diff) | |
[profiler] Add dedicated coverage profiler (#5622)
This is to remove the need to depend on the log profiler and mprof-report to generate code coverage reports
Diffstat (limited to 'man/mprof-report.1')
| -rw-r--r-- | man/mprof-report.1 | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/man/mprof-report.1 b/man/mprof-report.1 index 56663251bf8..45ea4f77b88 100644 --- a/man/mprof-report.1 +++ b/man/mprof-report.1 @@ -213,9 +213,6 @@ The following commands are available: .IP \[bu] 2 \f[I]nocounters\f[]: disables sampling of runtime and performance counters, which is normally done every 1 second. -.IP \[bu] 2 -\f[I]coverage\f[]: collect code coverage data. This implies enabling -the \f[I]calls\f[] option. .RE .SS Analyzing the profile data .PP @@ -338,8 +335,6 @@ version .IP \[bu] 2 \f[I]counters\f[]: counters samples .IP \[bu] 2 -\f[I]coverage\f[]: code coverage data -.IP \[bu] 2 \f[I]stats\f[]: event statistics .PP It is possible to limit some of the data displayed to a timeframe @@ -411,13 +406,6 @@ By default mprof-report will print the summary data to the console. To print it to a file, instead, use the option: .PP \f[B]--out=FILENAME\f[] -.SS Processing code coverage data -.PP -If you ran the profiler with the \f[I]coverage\f[] option, you can -process the collected coverage data into an XML file by running -mprof-report like this: -.PP -\f[B]mprof-report --coverage-out=coverage.xml output.mlpd\f[] .SS Dealing with profiler slowness .PP If the profiler needs to collect lots of data, the execution of the |