Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] A new command 'grep'
Date: Mon, 02 Jan 2012 08:54:00 -0000	[thread overview]
Message-ID: <E1Rhdf5-0002s7-UR@fencepost.gnu.org> (raw)
In-Reply-To: <CAGyQ6gwb0X8KTN8bzWKxzhCyTwN=zhjB=tuz1BNW-TX_KN-TyA@mail.gmail.com>	(message from Siva Chandra on Mon, 2 Jan 2012 10:30:55 +0530)

> Date: Mon, 2 Jan 2012 10:30:55 +0530
> From: Siva Chandra <sivachandra@google.com>
> 
> Attached is a patch which implements a 'grep' command using the GDB
> Python API. The idea behind the 'grep' command is as follows. We often
> have deep data structures and are probably interested in some one
> particular field or value embedded somewhere deep in that data
> structure. For such cases, instead of typing the complete expression
> for the field, we can use the 'grep' command to lookup the field or
> value of interest.

Thanks.

I think this is the first time we receive a proposal for a command
implemented in Python.  Perhaps there's a place to discuss whether
some policy is in order in this regard.  E.g., the command will be
unavailable in non-Python builds, which at least needs to be
documented.  There may be other aspects that are worth discussing.

If this is accepted, it will need user-level documentation.

I cannot say I like the name "grep".  Users will associate that name
with the Unix command that searches through files, which is radically
different from what your command does.  How about "lookup-fields"
instead?


  reply	other threads:[~2012-01-02  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02  5:01 Siva Chandra
2012-01-02  8:54 ` Eli Zaretskii [this message]
2012-01-02  9:28   ` Kevin Pouget
2012-01-02  9:35     ` Abhijit Halder
2012-01-02 10:17     ` Siva Chandra
2012-01-02 17:44     ` Doug Evans
2012-01-03  6:02       ` Siva Chandra

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=E1Rhdf5-0002s7-UR@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sivachandra@google.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