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.
"def replacement_colorize_disasm(content,gdbarch):" \
" return None" \
"gdb.styling.colorize_disasm = replacement_colorize_disasm" \
- "\004"] \
+ "end"] \
"setup replacement colorize_disasm function" \
true
" raise gdb.GdbError (\"miss-matched names\")" \
" if (r1 != r2):" \
" raise gdb.GdbError (\"miss-matched objects\")" \
- "\004" ] \
+ "end" ] \
"check names and objects match" 1
" raise gdb.GdbError (\"miss-matched names\")" \
" if (r1 != r2):" \
" raise gdb.GdbError (\"miss-matched objects\")" \
- "\004" ] \
+ "end" ] \
"check names and objects match" 1
# Ensure that the '.find' method on the iterator returns the same