Re: [patch v9 21/23] doc, record: document record changes

Jan Kratochvil
2013-03-05T20:13:49Z

On Mon, 04 Mar 2013 18:06:08 +0100, Markus Metzger wrote:
> Document changes to the record target resulting from the renaming into
> record-full.
>
> Document two new record sub-commands "record instruction-history" and
> "record function-call-history" and two associated set/show commands
> "set record instruction-history-size" and "set record
> function-call-history-size".
>
> Add this to NEWS.
>
> CC: Eli Zaretskii <eliz@gnu.org>
>
> 2013-03-04 Markus Metzger <markus.t.metzger@intel.com>
>
> * NEWS: Add record changes.
>
> doc/
> * gdb.texinfo (Process Record and Replay): Document record
> changes.
[...]
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,32 @@
>
> *** Changes since GDB 7.5
>
> +* Target record has been renamed to record-full.
> + Record/replay is now enabled with the "record full" command.
> + This also affects settings that are associated with full record/replay
> + that have been moved from "set/show record" to "set/show record full":
> +
> +record insn-number-max
> +record stop-at-limit
> +record memory-query

Eli has not commented the NEWS file it but I would prefer to provide
(a) the full/valid commmands, (b) the new, rather than old names,
so that one can easily copy-paste them to GDB CLI to try them.

set|show record full insn-number-max
set|show record full stop-at-limit
set|show record full memory-query

> +
> +* Two new commands have been added for record/replay to give information
> + about the recorded execution without having to replay the execution.
> +
> +"record instruction-history" disassembles instructions stored in the
> +execution log.
> +
> +"record function-call-history" prints the names of the functions
> +from instructions stored in the execution log.
> +
> +* A new record target "record-btrace" has been added. The new target
> + uses hardware support to record the control-flow of a process. It
> + does not support replaying the execution, but it implements the
> + above commands for investigating the recorded execution log.
> +
> + The "record-btrace" target is only available on Intel Atom processors
> + and requires a Linux kernel 2.6.32 or later.
> +
> * New native configurations
>
> ARM AArch64 GNU/Linux aarch64*-*-linux-gnu

Otherwise reviewed by Eli.

Thanks,
Jan