API: add `GDBDebugger >> getParameter:` and `setParameter:to:` ...to get / set GDB internal parameters such as prompt. The only complication here is that when a parameter is set by MI `-gdb-set` command, the `=cmd-param-changed' notification is not sent. This may or may not be a GDB bug. To make this transparent to `libgdbs` clients, intercept all `-gdb-set` commands and when sucessful, emit the event manually. This way, client may rely on value change notification (`GDBCmdParamChangedEvent`) to detect changes.

     1

struct _cons

     2

{

     3

  struct _cons *slots[2];

     4

};

     5

     6

#define nil ((struct _cons*)0);

     7

     8

int

     9

main (int argc, char **argv)

    10

{

    11

  struct _cons c1, c2, c3;

    12

    13

  c1.slots[0] = nil;

    14

  c1.slots[1] = &c2;

    15

    16

  c2.slots[0] = nil;

    17

  c2.slots[1] = &c3;

    18

    19

  c3.slots[0] = nil;

    20

  c3.slots[1] = nil;

    21

    22

  return 0;			/* next line */

    23

}