Pavel Labath 72ef113d40 [API] Have SBCommandReturnObject::GetOutput/Error return "" instead of nullptr ... Summary: It seems this was an unintended side-effect of D26698. AFAICT, these functions did return an empty string before that patch, and the patch contained code which attempted to ensure that, but those efforts were negated by ConstString::AsCString, which by default returns a nullptr even for empty strings. This patch: - fixes the GetOutput/Error methods to really return empty strings - adds and explicit test for that - removes a workaround in lldbtest.py, which was masking this problem from our other tests Reviewers: jingham, clayborg Subscribers: zturner, lldb-commits Differential Revision: https://reviews.llvm.org/D65739 llvm-svn: 368806		2019-08-14 08:11:20 +00:00
..
pre_kill_hook	added Linux support for test timeout sampling	2016-09-26 20:25:47 +00:00
support	[testsuite] Drop characters that can't be decoded, restoring parity with Py2.	2019-03-07 17:45:53 +00:00
test	[API] Have SBCommandReturnObject::GetOutput/Error return "" instead of nullptr	2019-08-14 08:11:20 +00:00
test_event	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00
__init__.py	*** This commit represents a complete reformatting of the LLDB source code	2016-09-06 20:57:50 +00:00
.clang-format	Updated .clang-format rules so bring LLDB in line with LLVM standards.	2016-09-06 17:19:00 +00:00