Re: [PATCH][TEST-CASE][DOC] Implementation of pipe to pass GDB's command output to the shell.

Abhijit Halder
2011-08-30T14:49:12Z

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.