aboutsummaryrefslogtreecommitdiff
path: root/gdb/language.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2018-12-01 08:56:56 +0100
committerTom de Vries <tdevries@suse.de>2018-12-01 08:56:56 +0100
commit64d27cfc97f5b865019f0b7293ff2b9565db427c (patch)
tree67cf9ee7df6b0f0b0562e414e186156e1928d68a /gdb/language.c
parent0acc7632bb09cce832a1b3756d31cc3fa93a724a (diff)
downloadgdb-64d27cfc97f5b865019f0b7293ff2b9565db427c.zip
gdb-64d27cfc97f5b865019f0b7293ff2b9565db427c.tar.gz
gdb-64d27cfc97f5b865019f0b7293ff2b9565db427c.tar.bz2
[gdb/testsuite] Add gdb-caching-proc.exp testcase
When caching a proc using gdb_caching_proc, it will become less likely to be executed, and consequently it's going to be harder to detect that the proc is racy. OTOH, in general the proc is easy to rerun. So, add a test-case to run all uncached gdb_caching_procs a number of times and detect inconsistent results. The purpose of caching is to reduce runtime, so rerunning is somewhat counter-productive in that aspect, but it's better than uncached, because the number of reruns is constant-bounded, and the increase in runtime is bound to this test-case, and can be disabled on slow targets. Tested on x86_64-linux. gdb/testsuite/ChangeLog: 2018-12-01 Tom de Vries <tdevries@suse.de> * gdb.base/gdb-caching-proc.exp: New file.
Diffstat (limited to 'gdb/language.c')
0 files changed, 0 insertions, 0 deletions