diff options
| author | Pavel Labath <labath@google.com> | 2015-03-20 11:24:36 +0000 |
|---|---|---|
| committer | Pavel Labath <labath@google.com> | 2015-03-20 11:24:36 +0000 |
| commit | 98236e0510de57b1d10d9e16d5c4a911a4ed7d88 (patch) | |
| tree | c4c58936ea93488a58e063df3618b60522ed857a /llvm/lib/ExecutionEngine/TargetSelect.cpp | |
| parent | 214997c63bc170b7859dcd03c551d6feaacb2dc2 (diff) | |
| download | bcm5719-llvm-98236e0510de57b1d10d9e16d5c4a911a4ed7d88.tar.gz bcm5719-llvm-98236e0510de57b1d10d9e16d5c4a911a4ed7d88.zip | |
Fix ninja check-lldb
Ninja apparently has issues with commands writing nul characters '\0' to stdout. When it
encounters a nul character, the rest of the output is skipped (I will file a bug with ninja about
that). This breaks the linux buildbot since it parses the ninja check-lldb output to get a list
of failures.
Recently, we have started outputting nul characters in lldb-server tests. This is probably
a bug in itself, but I am not addressing that now. This is just a workaround commit, which
prevents the nul characters from appearing in the output, and gets the buildbot operational again.
llvm-svn: 232805
Diffstat (limited to 'llvm/lib/ExecutionEngine/TargetSelect.cpp')
0 files changed, 0 insertions, 0 deletions
