| commit | 3573490bf0e5d2c550cebed5f4e1a8be0fab2c71 | [log] [tgz] |
|---|---|---|
| author | Tom de Vries <tdevries@suse.de> | Wed Jan 08 16:07:08 2025 +0100 |
| committer | Tom de Vries <tdevries@suse.de> | Wed Jan 08 16:07:08 2025 +0100 |
| tree | 5666f4036607e082c27afc669edafa9a6613009a | |
| parent | 9e5d27a53096033a5749e2001a0eca48e4b8b472 [diff] |
[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.