forked from Imagelibrary/binutils-gdb
cfc75767cc
While doing some changes, I managed to break this test in a way that running to main didn't work. However, it didn't produce any FAIL. I noticed because I diff'ed the results and saw some PASSes unexpectedly disappear, but that's a bit fragile. Add a fail in case this test fails to run to main. Ideally, I think that runto_main should by default produce a FAIL when it fails (the opposite of the existing logic), but that's a project of its own, so just fix this test for the moment. gdb/testsuite/ChangeLog: * gdb.base/continue-all-already-running.exp: Call fail if can't run to main. Change-Id: I84b816a126c92ac579ed5ebbe39b017bd5cb7096
82 lines
2.1 KiB
Plaintext
82 lines
2.1 KiB
Plaintext
# Copyright (C) 2014-2021 Free Software Foundation, Inc.
|
|
|
|
# This program is free software; you can redistribute it and/or modify
|
|
# it under the terms of the GNU General Public License as published by
|
|
# the Free Software Foundation; either version 3 of the License, or
|
|
# (at your option) any later version.
|
|
#
|
|
# This program is distributed in the hope that it will be useful,
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
# GNU General Public License for more details.
|
|
#
|
|
# You should have received a copy of the GNU General Public License
|
|
# along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
# Test that "c -a" doesn't leave GDB processing input, even if all
|
|
# threads were already running. PR gdb/17300.
|
|
|
|
standard_testfile
|
|
|
|
save_vars { GDBFLAGS } {
|
|
set GDBFLAGS "$GDBFLAGS -ex \"set non-stop on\""
|
|
if { [prepare_for_testing "failed to prepare" ${testfile} $srcfile] } {
|
|
return -1
|
|
}
|
|
}
|
|
|
|
if ![runto_main] {
|
|
fail "can't run to main"
|
|
return
|
|
}
|
|
|
|
set linenum [gdb_get_line_number "set break here"]
|
|
gdb_breakpoint "$linenum"
|
|
|
|
gdb_test "c -a&" "Continuing\\."
|
|
|
|
set test "no stop"
|
|
gdb_test_multiple "" $test {
|
|
-timeout 1
|
|
timeout {
|
|
pass $test
|
|
}
|
|
}
|
|
|
|
# Paranoia. Check that input works after bg command.
|
|
gdb_test "print 1" " = 1"
|
|
|
|
# Continue in the foreground, and wait one second to make sure the
|
|
# inferior really starts running. If we get a prompt to soon (e.g.,
|
|
# the program stops), this issues a fail.
|
|
set saw_continuing 0
|
|
set test "c -a"
|
|
gdb_test_multiple "c -a" $test {
|
|
-timeout 1
|
|
-re "Continuing\\." {
|
|
set saw_continuing 1
|
|
exp_continue
|
|
}
|
|
timeout {
|
|
gdb_assert $saw_continuing $test
|
|
}
|
|
}
|
|
|
|
# Type something while the inferior is running in the foreground.
|
|
send_gdb "print 2\n"
|
|
|
|
# Poor buggy GDB would crash before the breakpoint was hit.
|
|
set test "breakpoint hit"
|
|
gdb_test_multiple "" $test {
|
|
-re "set break here ..\r\n$gdb_prompt " {
|
|
pass $test
|
|
}
|
|
}
|
|
|
|
set test "print command result"
|
|
gdb_test_multiple "" $test {
|
|
-re " = 2\r\n$gdb_prompt $" {
|
|
pass $test
|
|
}
|
|
}
|