gdb/testsuite/gdb.server/stop-reply-no-thread-multi.exp

   1 # This testcase is part of GDB, the GNU debugger.
   2 #
   3 # Copyright 2021 Free Software Foundation, Inc.
   4 #
   5 # This program is free software; you can redistribute it and/or modify
   6 # it under the terms of the GNU General Public License as published by
   7 # the Free Software Foundation; either version 3 of the License, or
   8 # (at your option) any later version.
   9 #
  10 # This program is distributed in the hope that it will be useful,
  11 # but WITHOUT ANY WARRANTY; without even the implied warranty of
  12 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  13 # GNU General Public License for more details.
  14 #
  15 # You should have received a copy of the GNU General Public License
  16 # along with this program.  If not, see <http://www.gnu.org/licenses/>.
  17
  18 # Test how GDB handles the case where a target either doesn't use 'T'
  19 # packets at all or doesn't include a thread-id in a 'T' packet, AND,
  20 # where the test program contains multiple threads.
  21 #
  22 # In general if multiple threads are executing and the target doesn't
  23 # include a thread-id in its stop response then GDB will not be able
  24 # to correctly figure out which thread the stop applies to.
  25 #
  26 # However, this test covers a very specific case, there are multiple
  27 # threads but only a single thread is actually executing.  So, when
  28 # the stop comes from the target, without a thread-id, GDB should be
  29 # able to correctly figure out which thread has stopped.
  30
  31 load_lib gdbserver-support.exp
  32
  33 if { [skip_gdbserver_tests] } {
  34     verbose "skipping gdbserver tests"
  35     return -1
  36 }
  37
  38 standard_testfile
  39 if { [build_executable "failed to prepare" $testfile $srcfile {debug pthreads}] == -1 } {
  40     return -1
  41 }
  42
  43 # Run the tests with different features of GDBserver disabled.
  44 # TARGET_NON_STOP is passed to "maint set target-non-stop".
  45 proc run_test { target_non_stop disable_feature } {
  46     global binfile gdb_prompt decimal hex
  47     global GDBFLAGS
  48
  49     save_vars { GDBFLAGS } {
  50         append GDBFLAGS " -ex \"maint set target-non-stop $target_non_stop\""
  51         clean_restart ${binfile}
  52     }
  53
  54     # Make sure we're disconnected, in case we're testing with an
  55     # extended-remote board, therefore already connected.
  56     gdb_test "disconnect" ".*"
  57
  58     set packet_arg ""
  59     if { $disable_feature != "" } {
  60         set packet_arg "--disable-packet=${disable_feature}"
  61     }
  62     set res [gdbserver_start $packet_arg $binfile]
  63     set gdbserver_protocol [lindex $res 0]
  64     set gdbserver_gdbport [lindex $res 1]
  65
  66     # Disable XML-based thread listing, and multi-process extensions.
  67     gdb_test_no_output "set remote threads-packet off"
  68     gdb_test_no_output "set remote multiprocess-feature-packet off"
  69
  70     set res [gdb_target_cmd $gdbserver_protocol $gdbserver_gdbport]
  71     if ![gdb_assert {$res == 0} "connect"] {
  72         return
  73     }
  74
  75     # There should be only one thread listed at this point.
  76     gdb_test_multiple "info threads" "" {
  77         -re "2 Thread.*$gdb_prompt $" {
  78             fail $gdb_test_name
  79         }
  80         -re "has terminated.*$gdb_prompt $" {
  81             fail $gdb_test_name
  82         }
  83         -re "\\\* 1\[\t \]*Thread\[^\r\n\]*\r\n$gdb_prompt $" {
  84             pass $gdb_test_name
  85         }
  86     }
  87
  88     gdb_breakpoint "unlock_worker"
  89     gdb_continue_to_breakpoint "run to unlock_worker"
  90
  91     # There should be two threads at this point with thread 1 selected.
  92     gdb_test "info threads" \
  93         "\\\* 1\[\t \]*Thread\[^\r\n\]*\r\n  2\[\t \]*Thread\[^\r\n\]*" \
  94         "second thread should now exist"
  95
  96     # Switch threads.
  97     gdb_test "thread 2" ".*" "switch to second thread"
  98
  99     # Now turn on scheduler-locking so that when we step thread 2 only
 100     # that one thread will be set running.
 101     gdb_test_no_output "set scheduler-locking on"
 102
 103     # Single step thread 2.  Only the one thread will step.  When the
 104     # thread stops, if the stop packet doesn't include a thread-id
 105     # then GDB should still understand which thread stopped.
 106     gdb_test_multiple "stepi" "" {
 107         -re -wrap "Thread 1 received signal SIGTRAP.*" {
 108             fail $gdb_test_name
 109         }
 110         -re -wrap "$hex.*$decimal.*while \\(worker_blocked\\).*" {
 111             pass $gdb_test_name
 112         }
 113     }
 114
 115     # Check that thread 2 is still selected.
 116     gdb_test "info threads" \
 117         "  1\[\t \]*Thread\[^\r\n\]*\r\n\\\* 2\[\t \]*Thread\[^\r\n\]*" \
 118         "second thread should still be selected after stepi"
 119
 120     # Turn scheduler locking off again so that when we continue all
 121     # threads will be set running.
 122     gdb_test_no_output "set scheduler-locking off"
 123
 124     # Continue until exit.  The server sends a 'W' with no PID.
 125     # Bad GDB gave an error like below when target is nonstop:
 126     #  (gdb) c
 127     #  Continuing.
 128     #  No process or thread specified in stop reply: W00
 129     gdb_continue_to_end "" continue 1
 130 }
 131
 132 # Disable different features within gdbserver:
 133 #
 134 # Tthread: Start GDBserver, with ";thread:NNN" in T stop replies disabled,
 135 #          emulating old gdbservers when debugging single-threaded programs.
 136 #
 137 # T: Start GDBserver with the entire 'T' stop reply packet disabled,
 138 #    GDBserver will instead send the 'S' stop reply.
 139 #
 140 # Also test both all-stop and non-stop variants of the remote
 141 # protocol.
 142 foreach_with_prefix target-non-stop {"off" "on"} {
 143     foreach_with_prefix to_disable { "" Tthread T } {
 144         run_test ${target-non-stop} $to_disable
 145     }
 146 }