1 "{ Package: 'jv:libgdbs' }"

     2 

     3 GDBMICommand subclass:#GDBMI_info_gdb_mi_command

     4 	instanceVariableNames:''

     5 	classVariableNames:''

     6 	poolDictionaries:''

     7 	category:'GDB-Core-Commands-MI'

     8 !

     9 

    10 !GDBMI_info_gdb_mi_command class methodsFor:'documentation'!

    11 

    12 documentation

    13 "

    14 The `-info-gdb-mi-command' Command

    15 ----------------------------------

    16 

    17 Synopsis

    18 ........

    19 

    20       -info-gdb-mi-command CMD_NAME

    21 

    22    Query support for the GDB/MI command named CMD_NAME.

    23 

    24    Note that the dash (`-') starting all GDB/MI commands is technically

    25 not part of the command name (*note GDB/MI Input Syntax::), and thus

    26 should be omitted in CMD_NAME.  However, for ease of use, this command

    27 also accepts the form with the leading dash.

    28 

    29 {No value for `GDBN'} Command

    30 .............................

    31 

    32 There is no corresponding {No value for `GDBN'} command.

    33 

    34 Result

    35 ......

    36 

    37 The result is a tuple.  There is currently only one field:

    38 

    39 `exists'

    40      This field is equal to `'true'' if the GDB/MI command exists,

    41      `'false'' otherwise.

    42 

    43 

    44 Example

    45 .......

    46 

    47 Here is an example where the GDB/MI command does not exist:

    48 

    49      -info-gdb-mi-command unsupported-command

    50      ^done,command={exists='false'}

    51 

    52 And here is an example where the GDB/MI command is known to the

    53 debugger:

    54 

    55      -info-gdb-mi-command symbol-list-lines

    56      ^done,command={exists='true'}

    57 

    58 

    59 "

    60 ! !

    61 

    62 !GDBMI_info_gdb_mi_command methodsFor:'accessing'!

    63 

    64 operation

    65 	^ 'info-gdb-mi-command'

    66 ! !

    67