Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siva Chandra <sivachandra@google.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] A new command 'explore'
Date: Fri, 17 Feb 2012 10:09:00 -0000	[thread overview]
Message-ID: <CAGyQ6gxzmkm0YKuZiauHSQVMpjmiVg5qWF6KO8_BsRHb9_+yLg@mail.gmail.com> (raw)
In-Reply-To: <CADPb22QBVR-0JCjwvJ7fJRRMZAm6ytSmFsnArdb+1SaE0utQiw@mail.gmail.com>

> On Wed, Feb 8, 2012 at 1:33 AM, Siva Chandra <sivachandra@google.com> wrote:
>> Hello,
>>
>> I have not yet seen anything about a policy on contributions
>> implemented in extension languages. However, I have now implemented
>> the 'explore' command in C. The patch is attached. I will add
>> documentation after the basics of this patch are approved.
>>
>> 2012-02-08 Siva Chandra <sivachandra@google.com>
>>
>>         New command 'explore' which helps explore values in scope.
>>         * explore.c: Implemention of the 'explore' command.
>>         * Makefile.in: Add rules for compiling and linked explore.c.
>>         * testsuite/gdb.base/explore.c: C program used for testing
>>         the new 'explore' command.
>>         * testsuite/gdb.base/explore.exp: Tests for the new 'explore'
>>         command.
>>         * testsuite/gdb.base/Makefile.in: Add explore to EXECUTABLES
>

Doug > I'm not sure what others prefer, but I like the python version.
Doug > http://sourceware.org/ml/gdb-patches/2011-12/msg00831.html
Doug > Please write the docs, etc. for the python version, and I'll review
Doug > and approve it (modulo the docs, but Eli is pretty responsive).

BTW, did you mean that you prefer the python version because of its
better quality, or is it because of it being in python?

Thanks,
Siva Chandra


      parent reply	other threads:[~2012-02-17 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGyQ6gyAwr2zuv3NYpdk09vPyYpuFkyiErEhw-vws-WfuLDxiw@mail.gmail.com>
2011-12-19 19:05 ` Siva Chandra
2011-12-21 19:36   ` Tom Tromey
2011-12-22 11:00     ` Siva Chandra
2011-12-22  5:21   ` Joel Brobecker
2011-12-22 11:48     ` Siva Chandra
2011-12-22 12:53       ` Joel Brobecker
2011-12-27  6:29   ` Siva Chandra
2012-02-08  9:34     ` Siva Chandra
2012-02-17  7:40       ` Doug Evans
2012-02-17 10:00         ` Siva Chandra
2012-02-17 13:14           ` Phil Muldoon
2012-02-17 10:09         ` Siva Chandra [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=CAGyQ6gxzmkm0YKuZiauHSQVMpjmiVg5qWF6KO8_BsRHb9_+yLg@mail.gmail.com \
    --to=sivachandra@google.com \
    --cc=dje@google.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