summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2019-02-15 10:47:34 +0000
committerPavel Labath <pavel@labath.sk>2019-02-15 10:47:34 +0000
commit5f54fe2332ef3fcb34e20f5d62e6c2664d065ef1 (patch)
tree64291282f45b4c10048398f1cc1d4fd3bea1bf71 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
parenta00425ff0d04ac862a7990e3826f5aa00dad5d56 (diff)
downloadbcm5719-llvm-5f54fe2332ef3fcb34e20f5d62e6c2664d065ef1.tar.gz
bcm5719-llvm-5f54fe2332ef3fcb34e20f5d62e6c2664d065ef1.zip
Fix the gdb-client test suite for python3
This applies the same fix that was done in r354106 to the lldb-server test: bitcasting the string to a bytes object before sending it over a socket. Since the gdb-remote protocol occasionally contains binary data, and it does not assign any particular encoding to them, this is the right thing to do here. llvm-svn: 354114
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud