Fix incorrect "stopped" event handling

[roblourens]

From #181485

Need a better fix for the underlying issue at

vscode/src/vs/workbench/contrib/debug/common/debugModel.ts

Lines 1313 to 1336 in 5967add

	const wholeCallStack = new Promise<void>((c, e) => {
	topCallStack = thread.fetchCallStack(1).then(() => {
	if (!this.schedulers.has(thread.getId())) {
	this.schedulers.set(thread.getId(), new RunOnceScheduler(() => {
	thread.fetchCallStack(19).then(() => {
	const stale = thread.getStaleCallStack();
	const current = thread.getCallStack();
	let bottomOfCallStackChanged = stale.length !== current.length;
	for (let i = 1; i < stale.length && !bottomOfCallStackChanged; i++) {
	bottomOfCallStackChanged = !stale[i].equals(current[i]);
	}
	if (bottomOfCallStackChanged) {
	this._onDidChangeCallStack.fire();
	}
	c();
	});
	}, 420));
	}
	this.schedulers.get(thread.getId())!.schedule();
	this._onDidChangeCallStack.fire();
	});
	});

then to bring back the change from #181855

[roblourens]

When verifying, test with one of the multi-threaded examples here (#29168) the sample dev containers are helpful for getting a debug environment for C# or C++ too.

Previous issues:

• Exceptions not working properly #28536
• Test: Multi threaded delayed call stack fetching #29168
• Debugging AL Language #181485

[joyceerhl]

Still repros for me, I can't step past this line

[joyceerhl]

Hm, stopped and restarted the debug session, am now able to step over that second breakpoint 🤔 I'll consider this verified for now

[roblourens]

Not sure about that, but also all the issue reports have gone away so I think it's ok. I just tested it with C# for a bit and it's working fine for me.

[sim642]

The supposed fix doesn't really work though, it's still broken in 1.79: goblint/GobPie#60 (comment).

[roblourens]

I'm not following the comments in the issue, can you help me understand what is still an issue in vscode? A sample that I can repro would be great