All-Stop on top of Non-Stop

Non-stop allows finer grained control of threads. In the non-stop variant of the RSP, thread control is asynchronous.

We should get rid of the all-stop vs non-stop distinction. Itsets will allow merging the user interface aspects. On the backend side, we should implement all-stop behavior on top of the target always running in non-stop mode.

The remote target supports this mode since:

Though that is still not the default. You can activate the mode with "maint set target-non-stop on".

Native GNU/Linux target always works in non-stop mode by default.

1. Getting the code / Helping

Discussions are held on the main GDB mailing lists. Patches should be posted to the gdb-patches mailing list. Work is being committed directly to the mainline (i.e., there's no special feature branch).

2. Remaining sub tasks

2.1. Target independent (native/remote)

2.2. Remote target


None: AllStopOnTopOfNonStop (last edited 2016-02-17 00:40:22 by PedroAlves)

All content (C) 2008 Free Software Foundation. For terms of use, redistribution, and modification, please see the WikiLicense page.