[7/6] More gdb.threads/attach-into-signal.exp stale stopped bits (Re: [PATCH 6/6] Drop /proc/PID/status polling from gdb.threads/attach-into-signal.exp)
Commit Message
On 10/24/2017 08:27 AM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
>> gdb/testsuite/ChangeLog:
>> yyyy-mm-dd Pedro Alves <palves@redhat.com>
>>
>> * gdb.threads/attach-into-signal.exp: Remove whole "stoppedtry"
>> loop.
>
> Patch is good to me.
>
Hmmm, noticed a related stale bit further below. Here's a patch
that removes it.
From 8a645cfef64d4251f34f644792a756959ea440d4 Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Mon, 23 Oct 2017 17:46:07 +0100
Subject: [PATCH] More gdb.threads/attach-into-signal.exp stale stopped bits
This looks as stale as the other bit that was removed in a previous
commit. The test isn't attaching to a stopped process. (And if this
were generaly necessary, then it'd be better done from within
kill_wait_spawned_process.)
gdb/testsuite/ChangeLog:
2017-10-24 Pedro Alves <palves@redhat.com>
* gdb.threads/attach-into-signal.exp (corefunc): Don't SIGCONT
test program before killing it.
---
gdb/testsuite/gdb.threads/attach-into-signal.exp | 4 ----
1 file changed, 4 deletions(-)
@@ -113,10 +113,6 @@ proc corefunc { threadtype executable } {
# Exit and detach the process.
gdb_exit
- # Continue the program - some Linux kernels need it before -9 if the
- # process is stopped.
- remote_exec build "kill -s CONT ${testpid}"
-
kill_wait_spawned_process $test_spawn_id
}
}