From: Abhijit Halder <abhijit.k.halder@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org, sergiodj@redhat.com,
jan.kratochvil@redhat.com, tromey@redhat.com
Subject: Re: [PATCH][TEST-CASE][DOC] Implementation of pipe to pass GDB's command output to the shell.
Date: Tue, 30 Aug 2011 14:49:00 -0000 [thread overview]
Message-ID: <CAOhZP9y7mw4pOpWhitSHR1MuGjtb02D7Z1wFgiqkPnjhFVrUvg@mail.gmail.com> (raw)
In-Reply-To: <CAOhZP9yec-9MgFL1waa2Gm6xSqozFc3R=Gt9x-t81uXBq9iDOg@mail.gmail.com>
On Tue, Aug 30, 2011 at 8:01 PM, Abhijit Halder
<abhijit.k.halder@gmail.com> wrote:
> On Tue, Aug 30, 2011 at 7:57 PM, Pedro Alves <pedro@codesourcery.com> wrote:
>> On Tuesday 30 August 2011 14:58:02, Abhijit Halder wrote:
>>> +@table @code
>>> +@item pipe @var{args}
>>
>> I suggest writing this as something like:
>>
>> @item pipe @var{delim} @var{gdbcmd} @var{delim} @var{shellcmd}
>>
>> and then adjust the text a bit to refer to the variables by name.
>> The syntax is more immediately obvious this way.
>>
>>> +The @var{args} consists of a delimiter followed by a @value{GDBN} command,
>>> +followed by the same delimiter and finally a shell command. The delimiter is a
>>> +string of arbitrary length, containing no whitespace and no leading '-', acts
>>> +as a separator between a @value{GDBN} command and a shell command. The shell
>>> +command should be in compliance with the syntax of the default shell.
>>> +@end table
>>
>> --
>> Pedro Alves
>>
>
> Sure. I am going to change this.
>
Hi all,
In gdb.texinfo file I have seen @cindex and @kindex markup. Someone
please tell me the significance of them.
Secondly, the example I have used is from a sample code written by me
just for this purpose. This should not have any licensing issue I
hope.
next prev parent reply other threads:[~2011-08-30 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 11:43 Abhijit Halder
2011-08-26 12:18 ` Eli Zaretskii
2011-08-28 8:52 ` Abhijit Halder
2011-08-28 9:25 ` Eli Zaretskii
2011-08-28 9:51 ` Eli Zaretskii
2011-08-28 10:12 ` Eli Zaretskii
2011-08-30 13:58 ` Abhijit Halder
2011-08-30 14:27 ` Pedro Alves
2011-08-30 14:32 ` Abhijit Halder
2011-08-30 14:49 ` Abhijit Halder [this message]
2011-08-30 16:38 ` Abhijit Halder
2011-08-30 18:07 ` Eli Zaretskii
2011-08-31 8:44 ` Abhijit Halder
2011-08-31 11:01 ` Eli Zaretskii
2011-08-31 12:42 ` Abhijit Halder
2011-08-31 13:26 ` Eli Zaretskii
2011-08-30 18:09 ` Eli Zaretskii
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=CAOhZP9y7mw4pOpWhitSHR1MuGjtb02D7Z1wFgiqkPnjhFVrUvg@mail.gmail.com \
--to=abhijit.k.halder@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.com \
--cc=sergiodj@redhat.com \
--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