Task always launches when extension is activated

After the most recent release, the Cortex debug extension keeps launching and revealing a task window that says “Waiting for gdb server to start…” when being activated.

If this extension is being activated on more events than the configured debug resolution event, this is very disruptive. Extensions will always be activated when an extension that depends on them is activated, so if a user has an extension installed that lists this extension in extensionDependencies, the window will pop up as soon as the other extension is activated, making integration a bit awkward.

I’d suggest moving this task launch to somewhere other than the activate function, and potentially changing the task presentation configuration to not reveal itself by default. A configuration setting to disable this behavior altogether would also be handy.

[haneefdm]

Yes, that is my bad. I left it in there but it was supposed for Debug purposes. The automatic showing of the gdb-server terminal will not be there in the next release. Thanks for reporting this. Also, this only happens once for the first session. Definitely, not every time you launch the debugger. Also, I was trying to mirror the behavior we had before where the ‘Adapter Output’ window would show itself at the very start.

And no, this window will not move from the Terminal area. It was done to support semi-hosting and there is no other suitable place. And, it needs to look like a Terminal.

About activation, nope, this extension is not activated until you launch a cortex-debug session. As disruptive as it is, we don’t do it and I don’t see it on Windows and Mac. The following is our whole activation setup in package.json and it has been that way since day one.

    "activationEvents": [
        "onDebugResolve:cortex-debug"
    ],

So, unless VSCode is doing something … I don’t see how.

[haneefdm]

@trond-snekvik, There is an update that might help your situation. Changes have been pushed to the repo if you want to try it out. Also, there is a Reset device button that you could try out – I believe this was your suggestion.