mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 18:13:01 +00:00
c8ebba56ed
replaces r12124. His analysis of the testcase failure: I think I understand what is happening: even if the ptrace invoker functionality is not needed, the timeout to invoke might expire, which then leads to a message produced by vgdb if ptrace is restricted by the kernel. I think the best way to fix this is to add the option --max-invoke-ms=0 to vgdb. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@12130
15 lines
740 B
Plaintext
15 lines
740 B
Plaintext
# test that vgdb can invoke a process when all threads are in Runnable or Yielding mode
|
|
# If the test goes wrong, it might consume CPU during a long time.
|
|
prog: sleepers
|
|
args: 1 0 1000000000 B-B-B-B-
|
|
vgopts: --tool=memcheck --vgdb=yes --vgdb-prefix=./vgdb-prefix-mcinvokeRU
|
|
stderr_filter: filter_make_empty
|
|
# as the Valgrind process is always busy, we do not need the vgdb.ptraceinvoker prereq.
|
|
# We even disable ptrace invoker to avoid spurious attach error message
|
|
# on kernels where ptrace is restricted.
|
|
progB: invoker
|
|
argsB: 10 --vgdb-prefix=./vgdb-prefix-mcinvokeRU --max-invoke-ms=0 --wait=60 -c v.wait 0
|
|
# if the --wait is not enough, the test will fail or block.
|
|
stdoutB_filter: filter_memcheck_monitor
|
|
stderrB_filter: filter_vgdb
|