summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/options
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2019-02-13 13:06:37 +0000
committerPavel Labath <pavel@labath.sk>2019-02-13 13:06:37 +0000
commit3f27395322db8c296f10d8ca92a6d46801a6876d (patch)
tree1465d3b5c3a8675647fd025cff2fe7cab66c9145 /lldb/packages/Python/lldbsuite/test/expression_command/options
parent61a301e64521c9ad69d1a9f0968d6a6e3ad4043e (diff)
downloadbcm5719-llvm-3f27395322db8c296f10d8ca92a6d46801a6876d.tar.gz
bcm5719-llvm-3f27395322db8c296f10d8ca92a6d46801a6876d.zip
Revert "Fix one more string/bytes issue in lldb-server tests"
It looks like I was too hasty to submit the previous patch. It does fix some tests on python3, but it also breaks one tests with python2. This happens because the gdb-remote protocol can sometimes (but not very often) contain binary data, and attempting to parse this as utf8 characters fails. This reverts commit r353944. llvm-svn: 353945
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/options')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud