"trace-cmd report -f" functionality different than expected

[one one]

May be an unclear man page description or a bug. Tested on up to date ubuntu 18.04.4 LTS and 19.10 The command in question is:

trace-cmd report -f

From the man page:

-f: This outputs the list of functions that have been recorded in the file.

Expected result: Lists the functions that were traced (recorded in the .dat file)

Actual result: no matter what command was traced for the .dat, lists the same very large set of functions which appears to be similar to the entire /proc/kallsyms listing or all traceable functions, not just the ones that were traced. Without using the -f command, the report appears to be correct.

Note, the .dat is being generated by:

trace-cmd record -p function_graph -F <command>

where <command> is something like true, ls, ping, or those but in a loop

[Launchpad Janitor (janitor)]

This bug was fixed in the package trace-cmd - 2.9.1-1

---------------
trace-cmd (2.9.1-1) unstable; urgency=medium

  * Update to upstream v2.9.1
    - New version has updated manpages. (LP: #1868900)

 -- Sudip Mukherjee <email address hidden> Wed, 19 Aug 2020 20:51:17 +0100