[Bug gdb/17173] New: flag an error if non-stop tried in sync mode

["dje at google dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17173

            Bug ID: 17173
           Summary: flag an error if non-stop tried in sync mode
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

Non-stop "requires" async mode (*1), thus gdb should flag an error if the user
tries to use non-stop without async.  Async is now the default, but one can
still enable sync with "mt set target-async off", thus an error would still be
useful.  Plus while the docs use to include setting target-async when enabling
non-stop, they no longer do (which is fine), but the reader is now left with
more of a question of whether non-stop requires async.

Now that async is the default we should just simplify things and make the
requirement clear and absolute everywhere (docs and code).

---
(*1): e.g., ref: https://sourceware.org/gdb/wiki/AllStopOnTopOfNonStop

-- 
You are receiving this mail because:
You are on the CC list for the bug.