Fri, 27 Sep 2019 20:52:14 +0100 Fix `VDBVariableListApplication` w.r.t. `GDBVariable` that has no var-obj associated
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 27 Sep 2019 20:52:14 +0100] rev 187
Fix `VDBVariableListApplication` w.r.t. `GDBVariable` that has no var-obj associated ...such as when the variable is synthetic (provided by frame decorator)
Tue, 24 Sep 2019 00:43:53 +0100 Always inspect varobj when double-clicking on a variable
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 24 Sep 2019 00:43:53 +0100] rev 186
Always inspect varobj when double-clicking on a variable in variable inspector...
Sat, 21 Sep 2019 18:31:45 +0100 Do not try to raise transcript window if `Transcript` is not graphical
Jan Vrany <jan.vrany@fit.cvut.cz> [Sat, 21 Sep 2019 18:31:45 +0100] rev 185
Do not try to raise transcript window if `Transcript` is not graphical ...but - for instance - a `StdOut` or `StdErr`.
Fri, 20 Sep 2019 21:10:36 +0100 Fix finalization of `VDBVariableObject`
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 20 Sep 2019 21:10:36 +0100] rev 184
Fix finalization of `VDBVariableObject` Add missing `VDBVariableObject >> executor` returning specialized executor for VDB varobjs.
Fri, 06 Sep 2019 02:30:16 +0100 Fix `VDBStackApplication >> delayedUpdateAfterThreadStopped:`
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 06 Sep 2019 02:30:16 +0100] rev 183
Fix `VDBStackApplication >> delayedUpdateAfterThreadStopped:` ...so stopped frame is pre-selected as default. This commit essentially undo the change done in 364ebdd1d42c: Generalize `VDBInstructionListView`
Wed, 21 Aug 2019 22:53:15 +0100 Fix `VDBBariableObjectPresenter >> doDoubleClick:`
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 21 Aug 2019 22:53:15 +0100] rev 182
Fix `VDBBariableObjectPresenter >> doDoubleClick:`
Tue, 23 Jul 2019 14:53:07 +0100 Remove launcher script on UNIX
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 23 Jul 2019 14:53:07 +0100] rev 181
Remove launcher script on UNIX ...ie., `vdb` is the real executable, not just a script that launches it. Time have shown this laucnher script is not needed.
Tue, 23 Jul 2019 12:32:01 +0100 Add `VDBStartupA` into `jv:vdb/application`
Jan Vrany <jan.vrany@fit.cvut.cz> [Tue, 23 Jul 2019 12:32:01 +0100] rev 180
Add `VDBStartupA` into `jv:vdb/application` This class is just a placeholder, all logic is in its superclass, `VDBStatup`. The reason for this is the way the initial package path is computed (see `AbstractOpratingSystem >> defaultPackagePath`) The code there assumes that startup class is from the same package as the application itself. This way, we have a startup class in the application package but still have `VDBStartup` available when only `jv:vdb` is loaded (like when developing and.or using VDB from Smalltalk/X IDE.
Mon, 08 Jul 2019 23:12:19 +0100 UX: perform 'inspect' when variable is double-clicked
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 08 Jul 2019 23:12:19 +0100] rev 179
UX: perform 'inspect' when variable is double-clicked
Mon, 08 Jul 2019 13:31:11 +0100 Initial support for VDB python-based variable objects
Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 08 Jul 2019 13:31:11 +0100] rev 178
Initial support for VDB python-based variable objects Due to a limitation of GDB itself, one cannot create variable object for "synthetic" argument/local created by custom frame decorator. Therefore one cannot "dig deeper" and inspect contents of such a variable in case it is a kind of composite - like an object on a heap referring to another objects. This is a problem when a debugee is does not have debug information and / or it's language is not C - such as when debugging JITed code. This (experimental) commit adds a parallel implementation of variable objects done completely in python. This new varobj MI interface is a super-set of GDB's builtin varobj MI interface.
(0) -100 -10 +10 tip