Jan Vrany <jan.vrany@labware.com> [Tue, 09 Mar 2021 20:49:55 +0000] rev 219
Merge
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 02 Oct 2018 14:34:33 +0100] rev 218
Encapsulate event dispatch loop logic into single object - a `GDBEventDispatcher`
This is a preparation for nested event dispatch loops.
Jan Vrany <jan.vrany@labware.com> [Tue, 09 Mar 2021 12:29:05 +0000] rev 217
Backed out changeset 0509fe9ad879
Commit 0509fe9ad879 set option 'mi-always-notify' but support
for this will unlikely be upstreamed, see [1] and [2].
[1]: https://sourceware.org/pipermail/gdb/2019-June/047938.html
[2]: https://sourceware.org/pipermail/gdb/2019-June/047991.html
Jan Vrany <jan.vrany@labware.com> [Tue, 23 Feb 2021 13:38:11 +0000] rev 216
Update README
Add section on how to get started and an example use.
Jan Vrany <jan.vrany@labware.com> [Mon, 22 Feb 2021 19:55:25 +0000] rev 215
Add libgdbs API examples
...implemented as kind of tests in `GDBDebuggerExamples.st`
Jan Vrany <jan.vrany@labware.com> [Thu, 10 Dec 2020 20:11:56 +0000] rev 214
Add `GDBThread >> #name`
...returning either a thread name (if set) or target id of the thread.
Jan Vrany <jan.vrany@labware.com> [Wed, 11 Nov 2020 23:14:32 +0000] rev 213
Update documentation to refer to GitHub GDB repository
...rather than BitBucket one. There's no need for BitBucket
since they dropped Mercurial support.
Jan Vrany <jan.vrany@labware.com> [Mon, 19 Oct 2020 11:29:34 +0100] rev 212
Use `-iex` instead of `-ex` to execute initialization on GDB side
This makes them to execute before prompt is shown ans inferior
is loaded. Slightly nicer.
Jan Vrany <jan.vrany@labware.com> [Wed, 11 Nov 2020 23:12:37 +0000] rev 211
Use `#classVarAt:` and `#classVariableNames`
...instead of (gone) `#classVarNamed:` and `#classVariables`
Jan Vrany <jan.vrany@labware.com> [Mon, 10 Aug 2020 00:17:19 +0100] rev 210
Share "change holder" among all variable objects descending from a single parent
...to improve performance. `GDBVariableObject` tries to bulk-update
all variable object in one go in hope that savings for multiple GDB/MI
round trips would pay off for initial "hiccup".
However, we also have to share the "change holder" so when one variable
needs to ensure it's up-to-date (which in turn may lead to bulk-updating more),
then the other already knows it has been updated (or not) and need not
to make another GDB/MI round-trip.