Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Abhijit Halder <abhijit.k.halder@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH
Date: Tue, 12 Jul 2011 07:15:00 -0000	[thread overview]
Message-ID: <CAOhZP9w83=FF6khgRnmhV8ZfwiNgkhgitJX3tJsk_-=MLG=-4g@mail.gmail.com> (raw)
In-Reply-To: <CAOhZP9xxssgyoUuv05CVcA8RGkE1sDch+7fBet4dPiqk9fkejw@mail.gmail.com>

How if we just put a condition check whether the entered string after
pipe (|) is numeric. For e.g.
(gdb) thread apply all bt | grep foobar
Here the entered string after | is grep foobar which is not numeric.
But here (gdb) print var | 0x50 is numeric.

We may safely use this above notion as in case of any numeric file
name can be encapsulated within quote.

Soon I will submit the updated patch. Please provide feedback on this.

On Tue, Jul 12, 2011 at 5:01 AM, Abhijit Halder
<abhijit.k.halder@gmail.com> wrote:
> Yes I missed it. Let me modify the implementation to achieve the goal.
>
> On Tue, Jul 12, 2011 at 1:17 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>>> "Abhijit" == Abhijit Halder <abhijit.k.halder@gmail.com> writes:
>>
>> Abhijit> There is no way to pass the output of a gdb command to a shell
>> Abhijit> command. For example, something similar is not permitted: "(gdb)
>> Abhijit> thread apply all bt | vim -". This kind of feature is quite helpful in
>> Abhijit> a scenario where a program under debugger has 100s of threads running
>> Abhijit> and one wants to search a particular pattern in stack-traces. I have
>> Abhijit> implemented a feature which will allow one to pass the output of any
>> Abhijit> gdb command to any shell command.
>>
>> It would be nice to be able to do something like this.
>>
>> Abhijit> 2011-07-09 Abhijit Halder <abhijit.k.halder@symantec.com>
>> Abhijit>     * top.c (execute_command_to_pipe): New function.
>> Abhijit>      (execute_command): Update.
>>
>> I don't think this implementation is the right approach.
>> It does the wrong thing with some existing valid commands, e.g. "print x|5".
>>
>> Tom
>>
>


  reply	other threads:[~2011-07-12  4:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 13:09 PATCH Abhijit Halder
2011-07-09 19:06 ` PATCH oza Pawandeep
2011-07-11 12:13   ` PATCH Abhijit Halder
2011-07-11 13:42     ` PATCH Abhijit Halder
2011-07-10  7:47 ` PATCH Mike Frysinger
2011-07-11 21:10 ` PATCH Tom Tromey
2011-07-12  0:51   ` PATCH Abhijit Halder
2011-07-12  7:15     ` Abhijit Halder [this message]
2011-07-12  8:34       ` PATCH Mike Frysinger
2011-07-12  9:01         ` PATCH Abhijit Halder
2011-07-12 17:31           ` PATCH Mike Frysinger
2011-07-12 17:49             ` PATCH Matt Rice
2011-07-12 19:25               ` PATCH Mike Frysinger
2011-07-12 19:49       ` PATCH Tom Tromey
2011-07-12 20:43         ` PATCH Mike Frysinger
2011-07-13  8:45           ` PATCH Abhijit Halder
2011-07-15 14:15             ` PATCH Abhijit Halder
2011-07-15 20:49               ` PATCH Tom Tromey
2011-07-20 19:25               ` PATCH Sergio Durigan Junior
2011-07-21 11:08           ` gdb output pipelining to shell (was: Re: PATCH) Pedro Alves

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='CAOhZP9w83=FF6khgRnmhV8ZfwiNgkhgitJX3tJsk_-=MLG=-4g@mail.gmail.com' \
    --to=abhijit.k.halder@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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