search

bloombloombloom / Bloom

A debug interface for AVR-based embedded systems development on GNU/Linux.
https://bloom.oscillate.io/
Other
64 stars 3 forks source link

Activate the Insight window on-demand #79

Closed navnavnav closed 1 year ago

navnavnav commented 1 year ago

It's quite frustrating when I'm in the middle of a debug session with Insight disabled, and I realise that I need it.

Currently, I have to terminate the debug session, update bloom.yaml, then start a new debug session.

It would be nice if I could activate the Insight window during a debug session, using a GDB monitor command. Running something like monitor insight in the GDB console should bring up the Insight window.

More to follow.

navnavnav commented 1 year ago

Development work for this is mostly complete.

With the new monitor insight GDB command, the Insight GUI can be activated on-demand.

I've removed the enabled Insight config param and replaced it with the new acitvateOnStartup param:

insight:
  activateOnStartup: true

If set to true, the Insight GUI will be activated upon startup. But if it's set to false, the GUI can be activated on-demand via the GDB monitor command.

I've also prevented Bloom from triggering a shutdown when the user closes the main Insight window. I may allow this behaviour to be restored via an Insight config param, at a later date. For now, when a user closes the Insight GUI, Bloom will continue running and the user can reactivate the GUI via the new GDB monitor command.

I'll need to do more testing on this, after I've completed https://github.com/bloombloombloom/Bloom/issues/80, so I'm going to leave this open for now.