From: Hui Zhu <teawater@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>, Andi Kleen <andi@firstfloor.org>
Cc: gdb@sourceware.org
Subject: Re: record mode supposed to work on x86_64-linux?
Date: Sun, 17 May 2009 12:28:00 -0000 [thread overview]
Message-ID: <daef60380905170528j23b8c5b6s4a82f32515c9bf3f@mail.gmail.com> (raw)
In-Reply-To: <200905171252.01243.pedro@codesourcery.com>
Thank you very much Pedro and Andi.
I changed the changelog to:
2009-05-17 Hui Zhu <teawater@gmail.com>
* i386-tdep.c (i386_process_record): Make it extern.
(i386_gdbarch_init): Don't call set_gdbarch_process_record
here.
* i386-tdep.c (i386_process_record): Declare.
* i386-linux-tdep.c (i386_linux_init_abi): Call
set_gdbarch_process_record.
And checked-in.
Hui
On Sun, May 17, 2009 at 19:52, Pedro Alves <pedro@codesourcery.com> wrote:
> On Sunday 17 May 2009 01:15:00, Hui Zhu wrote:
>> Hi Pedro,
>>
>> What do you think about this one?
>
> I think it's good, thanks.
>
>> 2009-05-17 Hui Zhu <teawater@gmail.com>
>>
>> * i386-tdep.c (i386_process_record): Remove the static of it.
>> (i386_gdbarch_init): Remove the set_gdbarch_process_record.
>> * i386-tdep.c (i386_process_record): New extern.
>> * i386-linux-tdep.c (i386_linux_init_abi): Call
>> set_gdbarch_process_record.
>
> Please consider the alternative ChangeLog suggestions below instead.
>
>> * i386-tdep.c (i386_process_record): Remove the static of it.
>
> * i386-tdep.c (i386_process_record): Make it extern.
>
>> (i386_gdbarch_init): Remove the set_gdbarch_process_record.
>
> From this entry, it isn't clear what you're removing. Actually, it
> sounds like you're removing the function implementation. Consider
> instead:
>
> (i386_gdbarch_init): Remove the set_gdbarch_process_record call.
> ^^^^
>
> or even:
>
> (i386_gdbarch_init): Don't call set_gdbarch_process_record here.
>
>
>> * i386-tdep.c (i386_process_record): New extern.
>
> ^ typo
>
> * i386-tdep.h (i386_process_record): Declare.
>
> (`new extern' sounds like adding a new variable or function,
> but you're just changing the linkage of an existing function.)
>
> --
> Pedro Alves
>
next prev parent reply other threads:[~2009-05-17 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 18:41 Andi Kleen
2009-05-16 1:48 ` Hui Zhu
2009-05-16 8:05 ` Andi Kleen
2009-05-16 9:09 ` Hui Zhu
2009-05-16 9:21 ` Andi Kleen
2009-05-16 9:51 ` Hui Zhu
2009-05-16 11:54 ` Andi Kleen
2009-05-16 16:35 ` Pedro Alves
2009-05-17 0:15 ` Hui Zhu
2009-05-17 11:51 ` Pedro Alves
2009-05-17 12:28 ` Hui Zhu [this message]
2009-05-17 12:30 ` Pedro Alves
2009-05-17 12:40 ` 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=daef60380905170528j23b8c5b6s4a82f32515c9bf3f@mail.gmail.com \
--to=teawater@gmail.com \
--cc=andi@firstfloor.org \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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