aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.base/constvars.exp
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@efficios.com>2021-09-10 16:42:52 -0400
committerSimon Marchi <simon.marchi@polymtl.ca>2021-09-27 16:55:46 -0400
commitb45781ddac54c8d4b8d771d1f0823c4b5a072af3 (patch)
tree44cb58fae7453853d54f20e3d781ee4f10ffebf1 /gdb/testsuite/gdb.base/constvars.exp
parent09c0623ade7dcff1c5291a644397fdf714949edf (diff)
downloadgdb-b45781ddac54c8d4b8d771d1f0823c4b5a072af3.zip
gdb-b45781ddac54c8d4b8d771d1f0823c4b5a072af3.tar.gz
gdb-b45781ddac54c8d4b8d771d1f0823c4b5a072af3.tar.bz2
gdb.base/foll-fork.exp: refactor to restart GDB between each portion of the test
This test is difficult to follow and modify because the state of GDB is preserved some tests. Add a setup proc, which starts a new GDB and runs to main, and use it in all test procs. Use proc_with_prefix to avoid duplicates. The check_fork_catchpoints proc also seems used to check for follow-fork support by checking if catchpoints are supported. If they are not, it uses "return -code return", which makes its caller return. I find this unnecessary complex, versus just returning a boolean. Modify it to do so. Change-Id: I23e62b204286c5e9c5c86d2727f7d33fb126ed08
Diffstat (limited to 'gdb/testsuite/gdb.base/constvars.exp')
0 files changed, 0 insertions, 0 deletions