Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: oza Pawandeep <oza.pawandeep@gmail.com>
To: Matt Rice <ratmice@gmail.com>
Cc: Yao Qi <yao@codesourcery.com>,
		"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Makefile.in includes linux-record.c to be common for all arch. (arm-reversible>phase-3)
Date: Fri, 08 Jun 2012 12:45:00 -0000	[thread overview]
Message-ID: <CAK1A=4y3_XDNkz1gCmHRWqBcN5KxPfcr0JzT9vaJQRJu7JVsvg@mail.gmail.com> (raw)
In-Reply-To: <CACTLOFpgNkvxsYuc4Q60GR0KXSHSi09Siv3qrpPBSz=Datwacw@mail.gmail.com>

ok. It is clear now.
shall incorporate linux-record where Yao suggested.

Regards,
Oza.

On Fri, Jun 8, 2012 at 11:39 AM, Matt Rice <ratmice@gmail.com> wrote:
> On Thu, Jun 7, 2012 at 10:20 AM, oza Pawandeep <oza.pawandeep@gmail.com> wrote:
>> ok. sure will add it there as it is not currently linking.
>> but on the contrary 'record.o' is also under the same section
>> COMMON_OBS, which is also not required where no record support.
>> hence it is confusing.
>
> I think that because record.o implements gdb commands, we want
> commands to be available universally
> e.g. we want an error that support for a command is not available in a
> build of gdb, rather than 'Undefined command.'
>
> where linux-record appears to be plumbing, thus not necessary.


  reply	other threads:[~2012-06-08 12:45 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 [this message]
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
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=4y3_XDNkz1gCmHRWqBcN5KxPfcr0JzT9vaJQRJu7JVsvg@mail.gmail.com' \
    --to=oza.pawandeep@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ratmice@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