Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: oza Pawandeep <oza.pawandeep@gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Yao Qi <yao@codesourcery.com>
Subject: Re: [PATCH] Makefile.in includes linux-record.c to be common for all arch. (arm-reversible>phase-3)
Date: Mon, 18 Jun 2012 18:55:00 -0000	[thread overview]
Message-ID: <CAK1A=4yYjp4CaR+M47T6t7k2KPZA_KPxLzq2TzXh_OLJ9385Hg@mail.gmail.com> (raw)
In-Reply-To: <CAK1A=4wdqiGCGGQuQHmDB19O=RfjttaG9M83KpBkuUyQPd=0qQ@mail.gmail.com>

Hi Hui,

The phase2 works indepedently. It does not need syscall really. If i
recall correctly michael snyder suggested that i make two patches. The
first patch contains arm instructions and the second part contains
linux abi support.

The second part which i am working now requires linux-record.o hence i
wrote we require it to be compiled with the second part of patch.

So first i try to chek in minor change of configure.tgt and then i
check syscall record on arm; It has no dependency on any previous
arm-record stuffs.

By the way there is one more query which has been there under discussion.
When you made gdb sys call defination, it was thought as generic, but
it does not turn out to be applicable for arm as syscall number
differs. Sometime back tom had suggestion of having xml files under
gdb/syscalls  for arm arch and x86 separately; do you have any inputs
to it?  Of course it would change x86 syscall record to be read from
xml files.

Regards,
Oza.

On Tue, Jun 19, 2012 at 12:19 AM, oza Pawandeep <oza.pawandeep@gmail.com> wrote:
> Hi Hui,
>
> The phase2 works indepedently. It does not need syscall really. If i recall
> correctly michael snyder suggested that i make two patches.  The first patch
> contains arm instructions and the and second part contains linux abi
> support.
>
> The second part which i am working now requires linux-record.o hence i wrote
> we require it to be compiled with the second part of patch.
>
> So first i try to chek in minor change of congpfigure.tgt
> And then i check syscall record on arm.
>
> By the way there is one more query which has been there under discussion.
> When you made gdb sys call defination, it was thought as generic, but it
> does not turn out to be applicable for arm as syscall number differs.
> Sometime back tom had suggestion of having xml files under gdb/syscalls  for
> arm arch and x86 separately; do you have any inputs to it?  Of course it
> would change x86 syscall record to be read from xml files.j
>
> Regards,
> Oza.
>
> On Jun 18, 2012 2:22 PM, "Hui Zhu" <teawater@gmail.com> wrote:
>>
>> On Mon, Jun 18, 2012 at 7:49 PM, oza Pawandeep <oza.pawandeep@gmail.com>
>> wrote:
>> > Yes I agree; as I integrated both of them and post them at once.
>> > sorry about confusion; this patch has to be ignored.
>> >
>> > In fact I wanted this patch to be approved first because without which
>> > sys call patch would not compile.
>>
>>
>> Why you cannot commit a patch list when the function is done?
>> I think the function in the trunk tree need be done before commit to
>> it.  If you want work in cvs, I suggest you use the branch first.
>>
>> On the other hand, I heard that some of code of arm record is checked
>> in.  I don't think it is right.  Because without syscall support, it
>> cannot work, right?
>> So what I suggest is move all the code about arm record to a separate
>> branch.  And when all of the arm record function done, you re-send all
>> of them.
>>
>> Thanks,
>> Hui
>>
>>
>>
>> >
>> > Regards,
>> > Oza.
>> >
>> > On Mon, Jun 18, 2012 at 2:54 PM, Yao Qi <yao@codesourcery.com> wrote:
>> >> On 06/18/2012 05:08 PM, oza Pawandeep wrote:
>> >>> diff -urN orig/configure.tgt new/configure.tgt
>> >>> --- orig/configure.tgt        2012-06-18 12:36:47.274501400 +0530
>> >>> +++ new/configure.tgt 2012-06-18 12:31:47.335501400 +0530
>> >>> @@ -76,7 +76,7 @@
>> >>>  arm*-*-linux*)
>> >>>       # Target: ARM based machine running GNU/Linux
>> >>>       gdb_target_obs="arm-tdep.o arm-linux-tdep.o glibc-tdep.o \
>> >>> -                     solib-svr4.o symfile-mem.o linux-tdep.o"
>> >>> +                     solib-svr4.o symfile-mem.o linux-tdep.o
>> >>> linux-record.o"
>> >>>       build_gdbserver=yes
>> >>>       ;;
>> >>>  arm*-*-netbsd* | arm*-*-knetbsd*-gnu)
>> >>>
>> >>> ok to check in ?
>> >>
>> >> It is not good to post the same change twice in different mails.  This
>> >> change makes no sense until your 'arm-syscall record' patch is
>> >> approved.
>> >>  I noticed that this change has been included in your 'arm-syscall
>> >> record' patch, so I think patch here doesn't have to reviewed.
>> >>
>> >> --
>> >> Yao (齐尧)
>> >>
>> >>


  parent reply	other threads:[~2012-06-18 18:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  3:51 oza Pawandeep
2012-06-07 13:41 ` Yao Qi
2012-06-07 17:20   ` oza Pawandeep
2012-06-08  6:09     ` Matt Rice
2012-06-08 12:45       ` oza Pawandeep
2012-06-18  9:08         ` oza Pawandeep
2012-06-18  9:24           ` Yao Qi
2012-06-18 11:49             ` oza Pawandeep
2012-06-18 14:22               ` Hui Zhu
     [not found]                 ` <CAK1A=4wdqiGCGGQuQHmDB19O=RfjttaG9M83KpBkuUyQPd=0qQ@mail.gmail.com>
2012-06-18 18:55                   ` oza Pawandeep [this message]
2012-06-19  1:35                   ` Hui Zhu
2012-06-19  5:13                     ` oza Pawandeep
2012-06-19 16:03                       ` oza Pawandeep

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='CAK1A=4yYjp4CaR+M47T6t7k2KPZA_KPxLzq2TzXh_OLJ9385Hg@mail.gmail.com' \
    --to=oza.pawandeep@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.com \
    --cc=yao@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