From: teawater <teawater@gmail.com>
To: "Michael Snyder" <msnyder@vmware.com>
Cc: "Marc Khouzam" <marc.khouzam@ericsson.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Process record and replay, 8/10
Date: Mon, 10 Nov 2008 14:42:00 -0000 [thread overview]
Message-ID: <daef60380811100631o3341a952i1b8e01c049c7b4d7@mail.gmail.com> (raw)
In-Reply-To: <49148F1E.5090506@vmware.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2426 bytes --]
Sorry. I will talk it clear in the furue.
On Sat, Nov 8, 2008 at 02:55, Michael Snyder <msnyder@vmware.com> wrote:
> Marc,
>
> Try running gdbarch.sh, and then renaming the generated files appropriately.
>
> Looks like an oversight.
>
> Michael
>
>
> Marc Khouzam wrote:
>>
>> Hi,
>>
>> I just couldn't wait and wanted to try this out.
>> I applied all 10 patches, but my compilation fails.
>> cc1: warnings being treated as errors
>> ../../src/gdb/i386-tdep.c: In function 'i386_gdbarch_init':
>> ../../src/gdb/i386-tdep.c:5536: warning: implicit declaration of function
>> 'set_gdbarch_process_record'
>>
>> When I grep for gdbarch_process_record in the set of patches, I see some
>> new methods
>> being used but never declared. Am I missing a patch? Or have I been
>> coding with Java too long :-)
>>
>> Thanks
>>
>> Marc
>>
>>
>>> -----Original Message-----
>>> From: gdb-patches-owner@sourceware.org
>>> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of teawater
>>> Sent: Thursday, November 06, 2008 2:51 AM
>>> To: gdb-patches@sourceware.org
>>> Subject: [RFA] Process record and replay, 8/10
>>>
>>> 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(+)
>>>
>
>
\x16º&Öéj×!zÊÞ¶êççÞüÚX¬µªÜ\a[¥«\
ë
prev parent reply other threads:[~2008-11-10 14:32 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
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 [this message]
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=daef60380811100631o3341a952i1b8e01c049c7b4d7@mail.gmail.com \
--to=teawater@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=msnyder@vmware.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