Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: teawater <teawater@gmail.com>
To: "Doug Evans" <dje@google.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Process record and replay, 8/10
Date: Fri, 07 Nov 2008 02:02:00 -0000	[thread overview]
Message-ID: <daef60380811061802ga309f8bv5e2f20e895f64028@mail.gmail.com> (raw)
In-Reply-To: <e394668d0811060939x12f986afo1feeda3a18d43201@mail.gmail.com>

Thanks Doug,

Others told me it too. But I don't know how to do it is better.
Put "i386_process_record" to other file "i386-record".
Or keep it in i386-tdep but let it call other function in other file
"i386-record".

The second is clear, but it's low quality.

What do you guys think?

On Fri, Nov 7, 2008 at 01:39, Doug Evans <dje@google.com> wrote:
> On Wed, Nov 5, 2008 at 11:50 PM, teawater <teawater@gmail.com> wrote:
>> This patch add code to make I386 architecture support process record and replay.
>>
>> 2008-11-06  Hui Zhu  <teawater@gmail.com>
>>
>>        I386 architecture process record and replay support.
>>
>>        * i386-tdep.c (PREFIX_REPZ, PREFIX_REPNZ, PREFIX_LOCK,
>>        PREFIX_DATA, PREFIX_ADDR): New macros. Help decode the I386
>>        instruction.
>>        (aflag, dflag, override, modrm, mod, reg, rm, ot,
>>        i386_record_pc): New variables. Ditto.
>>        (i386_record_modrm, i386_record_lea_modrm_addr,
>>        i386_record_lea_modrm): New functions. Ditto.
>>        (i386_process_record): New function. Parse the instruction in
>>        address "addr" and record the values of registers and memory
>>        that will be change in this instruction.
>>        (i386_gdbarch_init): Set "i386_process_record" to GDBARCH
>>        "process_record" interface.
>>        * i386-tdep.h (gdbarch_tdep): New function pointers
>>        "i386_intx80_record" and "i386_sysenter_record" that point to
>>        the function can record "intx80" and "sysenter" execute log.
>>
>>  i386-tdep.c | 2706 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>  i386-tdep.h |    3
>>  2 files changed, 2709 insertions(+)
>>
>
> fwiw ...
>
> This is a case where I would REALLY like to see the code not live in
> i386-tdep.c.
> Maybe i386-tdep-<foo>.c?  i386-<foo>.c?
> Reverse execution is a significant enough and self-contained enough
> feature that it (and gdb) would be more maintainable with more
> isolation (so to speak).
> [insert my usual wistfulness regarding building applications out of libraries]
>


  reply	other threads:[~2008-11-07  2:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  7:51 teawater
2008-11-06 17:40 ` Doug Evans
2008-11-07  2:02   ` teawater [this message]
2008-11-07 15:34 ` Eli Zaretskii
2008-11-10 14:41   ` teawater
2008-11-10 14:51     ` Andreas Schwab
2008-11-10 17:45       ` teawater
2008-11-14 16:28     ` Eli Zaretskii
2008-11-14 17:18       ` teawater
2008-11-07 18:43 ` Marc Khouzam
2008-11-07 19:03   ` Michael Snyder
2008-11-10 14:42     ` teawater

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=daef60380811061802ga309f8bv5e2f20e895f64028@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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