]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
[gdb/testsuite] Require can_spawn_for_attach in gdb.base/gstack.exp
authorTom de Vries <tdevries@suse.de>
Wed, 8 Jan 2025 15:07:08 +0000 (16:07 +0100)
committerTom de Vries <tdevries@suse.de>
Wed, 8 Jan 2025 15:07:08 +0000 (16:07 +0100)
commit3573490bf0e5d2c550cebed5f4e1a8be0fab2c71
tree5666f4036607e082c27afc669edafa9a6613009a
parent9e5d27a53096033a5749e2001a0eca48e4b8b472
[gdb/testsuite] Require can_spawn_for_attach in gdb.base/gstack.exp

I ran test-case gdb.base/gstack.exp on a machine with kernel.yama.ptrace_scope
set to 1 and ran into:
...
PASS: gdb.base/gstack.exp: spawn gstack
ptrace: Operation not permitted.^M
GSTACK-END^M
PASS: gdb.base/gstack.exp: gstack exits with no error
PASS: gdb.base/gstack.exp: gstack's exit status is 0
FAIL: gdb.base/gstack.exp: got backtrace
...

Fix this by requiring can_spawn_for_attach.

Tested on x86_64-linux.
gdb/testsuite/gdb.base/gstack.exp