aboutsummaryrefslogtreecommitdiff
path: root/gdb/python/py-param.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-11-24 19:36:23 +0000
committerAndrew Burgess <aburgess@redhat.com>2023-02-04 16:15:38 +0000
commit79436bfc5aa71973f154b855f7440ed62ddd9582 (patch)
tree9cd2a0f518d51520282726bb27f533e073428393 /gdb/python/py-param.c
parentba268471bf9a2b76efc0d7a9c05291f7e8cd4424 (diff)
downloadgdb-79436bfc5aa71973f154b855f7440ed62ddd9582.zip
gdb-79436bfc5aa71973f154b855f7440ed62ddd9582.tar.gz
gdb-79436bfc5aa71973f154b855f7440ed62ddd9582.tar.bz2
gdb/testsuite: don't try to set non-stop mode on a running target
The test gdb.threads/thread-specific-bp.exp tries to set non-stop mode on a running target, something which the manual makes clear is not allowed. This commit restructures the test a little, we now set the non-stop mode as part of the GDBFLAGS, so the mode will be set before GDB connects to the target. As a consequence I'm able to move the with_test_prefix out of the check_thread_specific_breakpoint proc. The check_thread_specific_breakpoint proc is now called within a loop. After this commit the gdb.threads/thread-specific-bp.exp test still has some failures, this is because of an issue GDB currently has printing "Thread ... exited" messages. This problem should be addressed by this patch: https://sourceware.org/pipermail/gdb-patches/2022-December/194694.html when it is merged.
Diffstat (limited to 'gdb/python/py-param.c')
0 files changed, 0 insertions, 0 deletions