This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] An implementation of pipe to make I/O communication between gdb and shell.
- From: Pedro Alves <pedro at codesourcery dot com>
- To: Abhijit Halder <abhijit dot k dot halder at gmail dot com>
- Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, gdb-patches at sourceware dot org, Sergio Durigan Junior <sergiodj at redhat dot com>, Tom Tromey <tromey at redhat dot com>
- Date: Fri, 5 Aug 2011 10:56:58 +0100
- Subject: Re: [PATCH] An implementation of pipe to make I/O communication between gdb and shell.
- References: <CAOhZP9zU2K01zFDkChtutGT6yJjUeWYeGRNAAgPgM5rKwrgysg@mail.gmail.com> <20110805082947.GA5020@host1.jankratochvil.net> <CAOhZP9wr7LXfXwytiGRez_DnTUM-1XP9VPE4SiyhX=UT7tZJvQ@mail.gmail.com>
On Friday 05 August 2011 10:41:09, Abhijit Halder wrote:
> I am not sure whether this restriction is meaningful. Ideally we
> should not support any alpha-numeric character as a delimiter just
> because of readability purpose. e.g.
> (gdb) pipe dthread apply all btdvim -
> Here d is delimiter. I don't think the above one is acceptable. Please
> suggest me if we simply can put a restriction of not using any
> alpha-numeric character as delimiter and that will do.
> Secondly I believe by FOO you meant a single character and not a
> string. Between delimiter and command there is no restriction of
> having any white-space.
Speaking for myself, when I wrote PIPE and FOO before, I really
meant a string (with no whitespace), not a single character.
In your example above:
(gdb) pipe dthread apply all btdvim -
the delimiter would be `dthread'. I see no reason to
require it to be a single character.
--
Pedro Alves