binutils-gdb/gdb/testsuite/gdb.threads/stop-with-handle.exp

52 lines
1.9 KiB
Plaintext
Raw Normal View History

# Copyright 2019-2020 Free Software Foundation, Inc.
gdb: Don't ignore all SIGSTOP when the signal handler is set to pass It was observed that in a multi-threaded application on GNU/Linux, that if the user has set the SIGSTOP to be pass (using GDB's handle command) then the inferior would hang upon hitting a breakpoint. What happens is that when a thread hits the breakpoint GDB tries to stop all of the other threads by sending them a SIGSTOP and setting the stop_requested flag in the target_ops structure - this can be seen in infrun.c:stop_all_threads. GDB then waits for all of the other threads to stop. When the SIGSTOP event arrives we eventually end up in linux-nat.c:linux_nat_filter_event, which has the job of deciding if the event we're looking at (the SIGSTOP arriving in this case) is something that should be reported back to the core of GDB. One of the final actions of this function is to check if we stopped due to a signal, and if we did, and the signal has been set to 'pass' by the user then we ignore the event and resume the thread. This code already has some conditions in place that mean the event is reported to GDB even if the signal is in the set of signals to be passed to the inferior. In this commit I extend this condition such that: If the signal is a SIGSTOP, and the thread's stop_requested flag is set (indicating we're waiting for the thread to stop with a SIGSTOP) then we should report this SIGSTOP to GDB and not pass it to the inferior. With this change in place the test now passes. Regression tested on x86-64 GNU/Linux with no regressions. gdb/ChangeLog: * linux-nat.c (linux_nat_filter_event): Don't ignore SIGSTOP if we have just sent the thread a SIGSTOP and are waiting for it to arrive. gdb/testsuite/ChangeLog: * gdb.threads/stop-with-handle.c: New file. * gdb.threads/stop-with-handle.exp: New file.
2019-09-10 22:24:28 +08:00
#
# 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/>.
# This test covers a case where SIGSTOP has been configured to be
# passed to the target with GDB's 'handle' command, and then a
# multi-threaded inferior encounters an event that causes all theads
# to be stopped.
#
# The problem that (used) to exist was that GDB would see the SIGSTOP,
# but decide to ignore the signal based on the handle table.
standard_testfile
if {[prepare_for_testing "failed to prepare" \
"${testfile}" "${srcfile}" {debug pthreads}]} {
return -1
}
if ![runto_main] then {
fail "can't run to main"
return 0
}
# Have SIGSTOP sent to the inferior.
gdb_test "handle SIGSTOP nostop noprint pass" \
[multi_line \
"Signal\[ \t\]+Stop\[ \t\]+Print\[ \t\]+Pass to program\[ \t\]+Description" \
"SIGSTOP\[ \t\]+No\[ \t\]+No\[ \t\]+Yes\[ \t\]+Stopped \\(signal\\)"]
# Create a breakpoint, and when we hit it automatically finish the
# current frame.
gdb_breakpoint breakpt
# When the bug triggers this continue never completes. GDB hits the
# breakpoint in thread 1, and then tries to stop the second thread by
# sending it SIGSTOP. GDB sees the SIGSTOP arrive in thread 2 but
# incorrect decides to pass the SIGSTOP to the thread rather than
# bringing the thread to a stop.
gdb_continue_to_breakpoint breakpt