From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA/RFC Prec] Add Linux AMD64 process record support second version, (AMD64 Linux system call support) 3/3
Date: Mon, 13 Jul 2009 03:32:00 -0000 [thread overview]
Message-ID: <4A5A8438.6030005@vmware.com> (raw)
In-Reply-To: <daef60380907061940l6625d38p6b1a03a9527565ab@mail.gmail.com>
Hui Zhu wrote:
> Add prec support like i386-linux-tdep.c.
>
> 2009-07-07 Hui Zhu <teawater@gmail.com>
>
> Add Linux AMD64 process record support.
>
> * amd64-linux-tdep.c (amd64_linux_record_tdep): New variable.
> This struct has the argument for the function
> "record_linux_system_call".
> (amd64_linux_syscall_record): New function. Parse the
> system call instruction and call function
> "record_linux_system_call" to record execute log.
> (i386_linux_init_abi): Initialize "amd64_linux_record_tdep".
> Set "amd64_linux_syscall_record" to "i386_syscall_record".
Once again, just a preliminary review.
Same comments about space-after-cast etc.
> + /* Covent tmpulongest to number in record_linux_system_call. */
"Convert", maybe?
> + /* Initialize the amd64_linux_record_tdep. */
> + /* These values are the size of the type that will be used in a system
> + call. They are obtained from Linux Kernel source. */
> + amd64_linux_record_tdep.size_pointer = 8;
Can you use gdbarch_ptr_bit (gdbarch)?
> + amd64_linux_record_tdep.size_int = 4;
> + amd64_linux_record_tdep.size_long = 8;
> + amd64_linux_record_tdep.size_ulong = 8;
And again, aren't these sizes also in the gdbarch?
Do we need to duplicate them here?
next prev parent reply other threads:[~2009-07-13 0:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 2:40 Hui Zhu
2009-07-13 3:32 ` Michael Snyder [this message]
2009-07-17 12:45 ` Hui Zhu
2009-07-18 3:08 ` Michael Snyder
2009-07-19 17:19 ` Hui Zhu
2009-07-20 0:57 ` Michael Snyder
2009-07-19 21:03 ` Hui Zhu
2009-07-20 2:31 ` Michael Snyder
2009-07-20 14:13 ` Hui Zhu
2009-07-25 21:05 ` Michael Snyder
2009-07-26 1:14 ` Michael Snyder
2009-07-28 11:22 ` Hui Zhu
2009-08-03 5:41 ` Hui Zhu
2009-08-09 22:58 ` Michael Snyder
2009-08-10 3:15 ` Hui Zhu
2009-08-13 5:43 ` Michael Snyder
2009-07-14 22:19 ` Michael Snyder
2009-07-15 16:52 ` 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=4A5A8438.6030005@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb-patches@sourceware.org \
--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