From: Hui Zhu <teawater@gmail.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [Precord RFA/RFC] Add process record Linux system call 64 bits support
Date: Mon, 29 Jun 2009 08:34:00 -0000 [thread overview]
Message-ID: <daef60380906290133s23983809p2c3becb47c71f89b@mail.gmail.com> (raw)
In-Reply-To: <daef60380906210525l67bf5890w14bfd303a482cea3@mail.gmail.com>
Please goto http://sourceware.org/ml/gdb-patches/2009-06/msg00796.html
to get the new version.
On Sun, Jun 21, 2009 at 20:25, Hui Zhu<teawater@gmail.com> wrote:
> Add a very small comment, just 1 line.
>
> Thanks,
> Hui
>
> On Sat, Jun 20, 2009 at 16:04, Hui Zhu <teawater@gmail.com> wrote:
>>
>> Hi everyone,
>>
>> The linux-record has a lot of 32 bits special code (uint32_t and so
>> on). Then it can't support other bits.
>> I make a patch to remove all of them (Change them to ULONGEST and
>> extract_unsigned_integer) and make it support other bits better.
>>
>> 2009-06-19 Hui Zhu <teawater@gmail.com>
>>
>> Add process record Linux system call 64 bits support.
>>
>> * linux-record.h (linux_record_tdep): Add size_pointer,
>> size_size_t, size_iovec.
>> * i386-linux-tdep.c (i386_linux_init_abi): Ditto.
>> * linux-record.c (record_linux_system_call): Make this
>> function support 64 bits.
>>
>> Please help me review it.
>>
>> And I had post amd64 insn prec support in
>> http://sourceware.org/ml/gdb-patches/2009-06/msg00293.html
>> Please help me review it too.
>>
>> Thanks,
>> Hui
>
prev parent reply other threads:[~2009-06-29 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 8:04 Hui Zhu
2009-06-21 12:26 ` Hui Zhu
2009-06-29 8:34 ` Hui Zhu [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=daef60380906290133s23983809p2c3becb47c71f89b@mail.gmail.com \
--to=teawater@gmail.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