diff options
| author | Felix Willgerodt <felix.willgerodt@intel.com> | 2021-06-16 13:06:11 +0200 |
|---|---|---|
| committer | Felix Willgerodt <felix.willgerodt@intel.com> | 2021-06-16 13:55:25 +0200 |
| commit | cdb2186c9fa91b7f0b224eaaa3681db8dd196251 (patch) | |
| tree | 2716afa5b943981e2b5c2721e98f5b556d4cecb8 /sim | |
| parent | 8457e5ecc45295bc9550c4f705a276d5ca90d908 (diff) | |
| download | gdb-cdb2186c9fa91b7f0b224eaaa3681db8dd196251.zip gdb-cdb2186c9fa91b7f0b224eaaa3681db8dd196251.tar.gz gdb-cdb2186c9fa91b7f0b224eaaa3681db8dd196251.tar.bz2 | |
btrace, doc: Clarify record function-call-history documentation.
The documentation for 'record function-call-history' mentions lines instead
of functions when talking about the number of functions printed, as currently
there is only one line printed per function. Yet the code actually handles
this on function granularity not on line basis. Future patches will
extend the number of lines printed per function. This also makes it
consistent with the 'record instruction-history' command, where multiple
lines can be printed per instruction.
gdb/doc/ChangeLog:
2021-06-16 Felix Willgerodt <felix.willgerodt@intel.com>
* gdb.texinfo (Process Record and Replay): Stop mentioning lines
for "record function-call-history" and
"set record function-call-history-size".
Diffstat (limited to 'sim')
0 files changed, 0 insertions, 0 deletions