public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Wiederhake, Tim" <tim.wiederhake@intel.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"Metzger, Markus T" <markus.t.metzger@intel.com>,
	"brobecker@adacore.com"	<brobecker@adacore.com>
Subject: RE: [PATCH 5/8] Python: Introduce gdb.RecordGap class
Date: Wed, 19 Apr 2017 10:57:00 -0000	[thread overview]
Message-ID: <9676A094AF46E14E8265E7A3F4CCE9AF3C13EAC9@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <8637dc8fxf.fsf@gmail.com>

Hi Yao!

Renamed to reason_code / reason_string locally.

Regards,
Tim

> -----Original Message-----
> From: Yao Qi [mailto:qiyaoltc@gmail.com]
> Sent: Thursday, April 13, 2017 5:51 PM
> To: Wiederhake, Tim <tim.wiederhake@intel.com>
> Cc: gdb-patches@sourceware.org; Metzger, Markus T
> <markus.t.metzger@intel.com>; brobecker@adacore.com
> Subject: 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 (齐尧)
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

  reply	other threads:[~2017-04-19 10:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 14:59 [PATCH 0/8] Python bindings for GDB record Tim Wiederhake
2017-04-13 14:59 ` [PATCH 7/8] Python: Move and rename gdb.BtraceFunction Tim Wiederhake
2017-04-13 14:59 ` [PATCH 1/8] Python: Fix indentation in py-record-btrace.c Tim Wiederhake
2017-04-13 15:34   ` Yao Qi
2017-04-13 14:59 ` [PATCH 3/8] Python: Use correct ptid in btrace recording Tim Wiederhake
2017-04-20  9:41   ` Yao Qi
2017-04-20 13:43     ` Wiederhake, Tim
2017-04-20 14:15       ` Yao Qi
2017-04-13 14:59 ` [PATCH 2/8] Python: Fix exception handling in py-record-btrace.c Tim Wiederhake
2017-04-20  9:16   ` Yao Qi
2017-04-20 13:44     ` Wiederhake, Tim
2017-04-13 14:59 ` [PATCH 6/8] Python: Move and rename gdb.BtraceInstruction Tim Wiederhake
2017-04-20 11:46   ` Yao Qi
2017-04-20 13:43     ` Wiederhake, Tim
2017-04-20 14:21       ` Yao Qi
2017-04-13 14:59 ` [PATCH 5/8] Python: Introduce gdb.RecordGap class Tim Wiederhake
2017-04-13 15:50   ` Yao Qi
2017-04-19 10:57     ` Wiederhake, Tim [this message]
2017-04-13 14:59 ` [PATCH 8/8] Python: Introduce gdb.Instruction class Tim Wiederhake
2017-04-20 11:55   ` Yao Qi
2017-04-13 14:59 ` [PATCH 4/8] Python: Remove ptid from gdb.Record interface Tim Wiederhake
2017-04-13 15:38   ` Yao Qi
2017-04-13 15:20 ` [PATCH 0/8] Python bindings for GDB record Eli Zaretskii
2017-04-20 13:44   ` Wiederhake, Tim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9676A094AF46E14E8265E7A3F4CCE9AF3C13EAC9@IRSMSX106.ger.corp.intel.com \
    --to=tim.wiederhake@intel.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=markus.t.metzger@intel.com \
    --cc=qiyaoltc@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).