Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	  gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA/RFC Prec] Add Linux AMD64 process record support second  	version, (instruction set support) 1/3
Date: Sat, 25 Jul 2009 22:07:00 -0000	[thread overview]
Message-ID: <4A6B6FEC.8020904@vmware.com> (raw)
In-Reply-To: <daef60380907191016u67d99861oeac6e5b449b512af@mail.gmail.com>

Hui Zhu wrote:
> On Sat, Jul 18, 2009 at 07:53, Michael Snyder<msnyder@vmware.com> wrote:
>>> Thanks Michael,
>>>
>>> I updated all the AMD64 patches.  Please help me review it.
>>>
>>> Thanks,
>>> Hui
>>>
>>> 2009-07-17  Hui Zhu  <teawater@gmail.com>
>>>
>>>        Add AMD64 process record instruction set support.
>>>
>>>        * i386-tdep.h (gdbarch_tdep): Add record_regmap for registers
>>>        because the AMD64's registers order in GDB is not same with
>>>        I386 instructions.
>>>        Add i386_syscall_record to be the syscall function handle
>>>        interface.
>>>        (record_i386_regnum): Number for record_regmap.
>>>        * i386-tdep.c (OT_QUAD): For 64 bits.
>>>        (i386_record_s): Add rex_x, rex_b, rip_offset and
>>>        popl_esp_hack for AMD64 instruction set. And regmap for
>>>        record_regmap.
>>>        (i386_record_lea_modrm_addr): Support AMD64 instruction set
>>>        64 bits lea.
>>>        (i386_record_lea_modrm): Ditto.
>>>        (i386_record_push): New function.  Record the execution log
>>>        of push.
>>>        (I386_RECORD_ARCH_LIST_ADD_REG): New macro to record the
>>>        register.
>>>        (i386_process_record): Support AMD64 instruction set.
>>>        amd64-tdep.c (amd64_record_regmap): For record_regmap.
>> Should be a "*" at the beginning of the line above.

> Thanks Michael.
> 
> I update the patches according to your mail except changelog.  Because
> It sames that we just add * at the begin of the function name.

No, we add * before a file name.  Like this:

         * amd64-tdep.c (amd64_record_regmap): For record_regmap.
         (amd64_init_abi): Set amd64_record_regmap to record_regmap.


  parent reply	other threads:[~2009-07-25 20:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  2:38 Hui Zhu
2009-07-13  0:52 ` Michael Snyder
2009-07-17  8:50   ` Hui Zhu
2009-07-18  1:20     ` Michael Snyder
2009-07-19 17:21       ` Hui Zhu
2009-07-19 21:22         ` Mark Kettenis
2009-07-20  6:14           ` Hui Zhu
2009-07-20  1:39         ` Michael Snyder
2009-07-20 10:22           ` Hui Zhu
2009-07-20 14:24             ` Hui Zhu
2009-07-25 22:07         ` Michael Snyder [this message]
2009-07-27 16:50           ` Hui Zhu
2009-07-25 22:20         ` Michael Snyder
2009-07-28 11:03           ` Hui Zhu
2009-08-03  5:37             ` Hui Zhu

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=4A6B6FEC.8020904@vmware.com \
    --to=msnyder@vmware.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=teawater@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