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.
# automagically generated by the project definition
# this file is needed for stc to be able to compile modules independently.
# it provides information about a classes filename, category and especially namespace.
GDBDebuggeesResource GDBDebuggeesResource jv:libgdbs/tests 'GDB-Core-Tests' 1
GDBDebuggerTestCase GDBDebuggerTestCase jv:libgdbs/tests 'GDB-Core-Tests' 1
GDBInternalPipeStreamTests GDBInternalPipeStreamTests jv:libgdbs/tests 'GDB-Support-Tests' 1
GDBMIParserTests GDBMIParserTests jv:libgdbs/tests 'GDB-Private-Tests' 1
GDBMIPrinterTests GDBMIPrinterTests jv:libgdbs/tests 'GDB-Private-Tests' 1
GDBTransientDataHolderTests GDBTransientDataHolderTests jv:libgdbs/tests 'GDB-Private-Tests' 1
jv_libgdbs_tests jv_libgdbs_tests jv:libgdbs/tests '* Projects & Packages *' 3
GDBDebuggerTestsR GDBDebuggerTestsR jv:libgdbs/tests 'GDB-Core-Tests' 1