Provide "refresh all" type operation

[jonahgraham]

I am not sure where (or how many levels) in this stack need to be addressed for this.

Right now if something in the UI becomes out of sync with gdb, there isn't really a way to recover. Users can do continue/pause in the CLI and that may return the UI to the correct state. In CDT we have a "refresh all" command that tells the client/adapter (or their Eclipse equivalents) to re-fetch all state from gdb.

In practice this out of sync doesn't happen often, but sometimes when threads start/stop quickly the overall state can become incorrect.

[jreineckearm]

Loosely related issue #402 / PR #415 .

Would be interesting to understand what such refresh includes. In particular how to refresh knowledge about run/pause state of target.

[jonahgraham]

Would be interesting to understand what such refresh includes.

In Eclipse CDT it refreshes everything - all state in the IDE is supposed to be discarded and re-fetched from GDB.

In particular how to refresh knowledge about run/pause state of target.

In Eclipse CDT since we control the whole stack this isn't a big problem. I think we can achieve something along the same lines by issuing invalidated event perhaps? But I haven't experimented with it.