Description Marc Khouzam 2017-01-31 16:14:30 EST

It was suggested (see https://dev.eclipse.org/mhonarc/lists/cdt-dev/msg31626.html) that we could automatically figure out if a target supports non-stop and then choose that automatically for a user.

We should then update the preferences to be:
- always all-stop
- non-stop if available

Since reverse debug does not work in non-stop, we'd have to figure out the best way to deal with it.  We could simply force all-stop when reverse is selected in the launch; if the user wanted to turn on reverse later in a session though, there would be no way to do it if we constantly ran non-stop; the user would have to understand they must run all-stop (kind of how it is right now...).