With multiple real target launches, debug operation changes call stack selection

I'm testing using two debug launches (Real hardware debugging) in windows, cdt-gdb-vscode v0.0.108 is used. When continuously stepping on one launch, with other launch suspended, the call stack suddenly switches to suspended launch. If I continue stepping, the second launch is being stepped.

This is a wired behavior. Please let me guide on where to be focused to fix the issue.

Note : Issue is not reproducible with local debugging (Tried using amalgamator workspace https://github.com/eclipse-cdt-cloud/cdt-amalgamator )

@jonahgraham @MatthewKhouzam @thegecko @marco-miller