This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/8] Python: Introduce gdb.RecordGap class
Tim Wiederhake <tim.wiederhake@intel.com> writes:
> +If an error occured during recording or decoding a recording, this error is
> +represented by a @code{gdb.RecordGap} object in the instruction list. It has
IMO, RecordGap is a hole in instruct trace, it can be caused by error,
but can be caused by something else. Suppose GDB wants to trace four
instructions in every five instructions, that means there will be a gap
after every four instructions.
In current implementation, the gap is caused by error, but we don't have
to limit the interface to so.
> +the following attributes:
> +
> +@defvar RecordGap.number
> +An integer identifying this gap. @var{number} corresponds to the numbers seen
> +in @code{record instruction-history} (@pxref{Process Record and Replay}).
> +@end defvar
> +
> +@defvar RecordGap.error_code
How about RecordGap.reason_code?
> +A numerical representation of the reason for the gap. The value is specific to
> +the current recording method.
> +@end defvar
> +
> +@defvar RecordGap.error_string
> +A human readable string with the reason for the gap.
and RecoardGap.reason_string?
> @end defvar
>
--
Yao (齐尧)