diff options
author | Andrew Burgess <aburgess@redhat.com> | 2022-10-08 16:58:00 +0100 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2022-10-10 10:23:59 +0100 |
commit | f91822c2b9f9fed0c2717b17f380e5216502ea32 (patch) | |
tree | fd5544e6971169bd13dbb48c7a4a209bba586a73 /gdb/s390-tdep.c | |
parent | d549d8d23db0c12986d98bcb8e393939409237b5 (diff) | |
download | gdb-f91822c2b9f9fed0c2717b17f380e5216502ea32.zip gdb-f91822c2b9f9fed0c2717b17f380e5216502ea32.tar.gz gdb-f91822c2b9f9fed0c2717b17f380e5216502ea32.tar.bz2 |
gdb/testsuite: use 'end' at the end of python blocks
Within the testsuite, use the keyword 'end' to terminate blocks of
Python code being sent to GDB, rather than sending \004. I could only
find three instances of this, all in tests that I originally wrote. I
have no memory of there being any special reason why I used \004
instead of 'end' - I assume I copied this from somewhere else that has
since changed.
Non of the tests being changed here are specifically about whether
\004 can be used to terminate a Python block, so I think switching to
the more standard 'end' keyword is the right choice.
Diffstat (limited to 'gdb/s390-tdep.c')
0 files changed, 0 insertions, 0 deletions