[PATCH 4/4 v2] Test non-leader exec events in non-stop mode

["Breazeal, Don" <donb at codesourcery dot com>]

This patch extends the non-ldr-exc-*.exp tests so that they run all their cases in non-stop mode as well as all-stop mode.  These tests cover handling of exec events when non-leader threads call exec.

Fixed problems in the previous version of this patch to get all the tests working correctly for native gdb, contrary to what I stated in the patch 0 email of this series.  The tests also report a test error when 'runto_main' fails.  In non-stop mode with 'target extended-remote', runto_main always fails with something like:

(gdb) run ^M
Starting program: /scratch/dbreazea/gdb-nat2/mine/gdb/testsuite/gdb.threads/non-ldr-exc-4
Unexpected vCont reply in non-stop mode: T0506:10e0ffffff7f0000;07:c8deffffff7f0000;10:c1a6abaaaa2a0000;thread:p5ee.5ee;core:0;

This happens in other tests as well (e.g. gdb.threads/thread_events.exp), so I copied the error handling from that test so that the non-stop tests report 'untested' for target extended-remote.  I couldn't find anything related to this in the gdb bug database, but I assume it is a known problem since the other tests handle it.

--Don

2014-04-03  Don Breazeal  <donb@codesourcery.com>

        * gdb/testsuite/gdb.threads/non-ldr-exc-1.exp: Add non-stop cases,
        call 'untested' if 'runto_main' fails.
        * gdb/testsuite/gdb.threads/non-ldr-exc-2.exp: Ditto.
        * gdb/testsuite/gdb.threads/non-ldr-exc-3.exp: Ditto.
        * gdb/testsuite/gdb.threads/non-ldr-exc-4.exp: Ditto.

Attachment: 0004v2-remote-exec-test.patch
Description: 0004v2-remote-exec-test.patch