forked from Imagelibrary/binutils-gdb
26011e4e10
With a gdb 16.2 based package, I ran into: ... (gdb) PASS: gdb.base/bg-execution-repeat.exp: c 1&: input still accepted interrupt (gdb) PASS: gdb.base/bg-execution-repeat.exp: c 1&: interrupt set var do_wait=0 (gdb) PASS: gdb.base/bg-execution-repeat.exp: c 1&: set var do_wait=0 continue& Cannot execute this command while the selected thread is running. (gdb) Program received signal SIGINT, Interrupt. PASS: gdb.base/bg-execution-repeat.exp: c 1&: continue& 0x00007ffff7cf1503 in clock_nanosleep@GLIBC_2.2.5 () from /lib64/libc.so.6 FAIL: gdb.base/bg-execution-repeat.exp: c 1&: breakpoint hit 2 (timeout) ... Fix this by waiting for "Program received signal SIGINT, Interrupt" after issuing the interrupt command. Tested on x86_64-linux.
102 lines
2.8 KiB
Plaintext
102 lines
2.8 KiB
Plaintext
# Copyright (C) 2014-2025 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 repeating a background command doesn't lose the "&" in the
|
|
# repeat, turning a background command into a foreground command. See
|
|
# PR gdb/17471.
|
|
|
|
standard_testfile
|
|
|
|
if { [build_executable "failed to prepare" ${testfile} $srcfile] } {
|
|
return -1
|
|
}
|
|
|
|
set linenum [gdb_get_line_number "set break here"]
|
|
|
|
# Run the test proper. CONTINUE_CMD is the background continue
|
|
# command to issue.
|
|
|
|
proc test {continue_cmd} {
|
|
global gdb_prompt
|
|
global binfile
|
|
global linenum
|
|
|
|
clean_restart $binfile
|
|
|
|
if ![runto_main] {
|
|
return
|
|
}
|
|
|
|
gdb_breakpoint "$linenum"
|
|
|
|
# If the breakpoint triggers soon enough we see further output after the
|
|
# prompt, so no prompt anchor.
|
|
gdb_test -no-prompt-anchor $continue_cmd [string_to_regexp "Continuing."]
|
|
|
|
# Wait for the stop. Don't expect a prompt, as we had resumed the
|
|
# inferior in the background.
|
|
set test "breakpoint hit 1"
|
|
gdb_test_multiple "" $test {
|
|
-re "set break here" {
|
|
pass $test
|
|
}
|
|
}
|
|
|
|
# Trigger a repeat. Buggy GDB used to lose the "&", making this a
|
|
# foreground command...
|
|
send_gdb "\n"
|
|
gdb_test "" "Continuing\\." "repeat bg command"
|
|
|
|
# ... and thus further input wouldn't be processed until the target
|
|
# stopped.
|
|
gdb_test "print 1" " = 1" "input still accepted"
|
|
|
|
# With gdbserver, we cannot set memory while the inferior is running, so
|
|
# enable the "set var" command with an interrupt / continue& pair.
|
|
gdb_test -no-prompt-anchor "interrupt"
|
|
|
|
set test "interrupt received"
|
|
set re [string_to_regexp "Program received signal SIGINT, Interrupt."]
|
|
gdb_expect {
|
|
-re $re {
|
|
pass $test
|
|
}
|
|
timeout {
|
|
fail "$test (timeout)"
|
|
}
|
|
}
|
|
|
|
# Allow the breakpoint to trigger.
|
|
gdb_test -no-prompt-anchor "set var do_wait=0"
|
|
|
|
gdb_test -no-prompt-anchor "continue&"
|
|
|
|
# Make sure we see a stop after the print, and not before. Don't
|
|
# expect a prompt, as we had resumed the inferior in the background.
|
|
set test "breakpoint hit 2"
|
|
gdb_test_multiple "" $test {
|
|
-re "set break here ..\r\n" {
|
|
pass $test
|
|
}
|
|
}
|
|
}
|
|
|
|
# Test with and without extra arguments.
|
|
foreach cmd {"c&" "c 1&"} {
|
|
with_test_prefix $cmd {
|
|
test $cmd
|
|
}
|
|
}
|