diff options
author | Andrew Burgess <andrew.burgess@embecosm.com> | 2019-03-23 22:49:09 +0000 |
---|---|---|
committer | Andrew Burgess <andrew.burgess@embecosm.com> | 2019-03-26 18:23:50 +0000 |
commit | 3714a195e08a5cc7713b27def7a3c3b534da53e8 (patch) | |
tree | 49709881cade829bc63451c0709083eb4cb3f68b /gdb/testsuite/gdb.python/py-prettyprint.py | |
parent | 18c77628b1e97e412561029ec20195c1ffa61b2d (diff) | |
download | binutils-3714a195e08a5cc7713b27def7a3c3b534da53e8.zip binutils-3714a195e08a5cc7713b27def7a3c3b534da53e8.tar.gz binutils-3714a195e08a5cc7713b27def7a3c3b534da53e8.tar.bz2 |
gdb/testsuite: Make test names unique in gdb.python/py-prettyprint.exp
This makes the test names unique in gdb.python/py-prettyprint.exp, it
also switches to use gdb_breakpoint and gdb_continue_to_breakpoint
more so that we avoid test names with the source line number in - this
is bad if the test source ever changes as the test names will then
change.
One final change is to switch from using gdb_py_test_silent_cmd to use
gdb_test_no_output, the former should be used for running python
commands and can catch any thrown exception. However, in this case
the command being run is not a python command, its just a normal GDB
CLI command that produces no output, so lets use the appropriate
wrapper function.
gdb/testsuite/ChangeLog:
* gdb.python/py-prettyprint.exp: Use gdb_breakpoint and
gdb_continue_to_breakpoint more throughout this test.
(run_lang_tests) Supply unique test names, and use
gdb_test_no_output.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-prettyprint.py')
0 files changed, 0 insertions, 0 deletions