Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Reseting the embedded target does not update the editor location

Hi Torbjörn,

I think the correct solution is to have the views listen to the ICommandControlRefreshAllDMEvent. I think this carries on from the work we did together a few years ago in


Jonah Graham
Kichwa Coders

On Tue, 25 Jan 2022 at 12:35, Torbjorn SVENSSON via cdt-dev <cdt-dev@xxxxxxxxxxx> wrote:

In our Cortex-M IDE, we have a toolbar button that will reset the embedded target by sending the 'monitor reset' command to the GDB server. Doing so will obviously reset some IP's in the target and also change $pc to use the 2nd word in the vector as that's the location of the first instruction of the program.

This button works fine for the overall picture, but the state of some of the CDT views is not correct after the reset.
Some views, like the "Debug" view shows the correct content after we call:
fTracker.getService(ICommandControlService.class). flushAllCachesAndRefresh(rm);

Other views, like the editor or "Disassembly" view are still stuck on the location prior to the reset. The only way to make them aware of the change of state is to either have GDB fire a new suspend-event or manually re-select the frame in the "Debug" view.

Is there some way to manually trigger a suspend-event from an instance of org.eclipse.cdt.dsf.concurrent.Sequence or any other way to make the views know that they need to refresh?

Kind regards,
cdt-dev mailing list
To unsubscribe from this list, visit

Back to the top