|Re: [cdt-dev] CDT Call Wednesday (today!)|
Thanks for the clarification, I have that one checked because without it will try to relaunch new sessions without terminating the previous one and with our embedded targets we can have only one session at the same time. So if we want to launch new one, we have to terminate the current one.
When it's checked it terminates first which is good and tries to relaunch the last session again, which is good as well, just the re-launch is happening too fast and or HW/OpenOCD/setup is not ready to accept new session yet.
We in essence slowed down the termination of the starter.exe and it takes more time, while the CDT still expect the original "instant" behavior and continues launching new session just tiny bit too quickly. If the CDT would check for starter.exe being terminated then if it's configured to be instant then CDT would be instant and default behavior for most users wouldn't change. If the starter would be slower then CDT would just follow the suit.
From: cdt-dev <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Torbjorn SVENSSON via cdt-dev <cdt-dev@xxxxxxxxxxx>
Sent: 14 October 2021 10:08
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Cc: Torbjorn SVENSSON <torbjorn.svensson@xxxxxx>
Subject: Re: [cdt-dev] CDT Call Wednesday (today!)
Just a small clarification on the starter.exe topic below in the MoM:
There is no property for how the starter.exe work, but there is a property for how eclipse will handle terminate and relaunch.
After discussion with my teammates, the option that I was thinking about is:
Thanks all for coming. Please have a look at the minutes below
On Wed, 13 Oct 2021 at 09:41, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Back to the top