"Continue" currently says that if it can't continue just one thread, it should continue all threads.

The protocol shouldn't specify a fallback on different behavior - instead the continue request should fail, while a continue request without a threadID should mean "continue all threads".

@weinand:

I agree that the fallback semantics is a bad idea. Please file DAP protocol bug for this.

But please note that it might be impossible to fix this in the current version of the DAP in a non-breaking way.

cc
@mostafaeweda
@ebluestein