summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/scope/main.cpp
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2016-02-04 09:53:33 +0000
committerPavel Labath <labath@google.com>2016-02-04 09:53:33 +0000
commitfcf08db0f9fb5f3e12d72d0ae0151c7742b7933f (patch)
tree0f0ade38511ff8f0d9de0522ce7249a188f0a1db /lldb/packages/Python/lldbsuite/test/lang/cpp/scope/main.cpp
parent0d2bfcfb34de6d1d54e544c8ec4551f0733cdb15 (diff)
downloadbcm5719-llvm-fcf08db0f9fb5f3e12d72d0ae0151c7742b7933f.tar.gz
bcm5719-llvm-fcf08db0f9fb5f3e12d72d0ae0151c7742b7933f.zip
Add verbose logging support to gdb-remote tests
Summary: gdb-remote tests are not able to use the same logging mechanisms as the rest of our tests, and currently we get no host logs from them, even though the tests themselves have logging capability. This commit changes that. When user specifies that he would like to log the gdb-remote channel (--channel gdb-remote argument to dotest.py), we write detailed logs to the <TEST_ID>-host.log file, just like we would in the case of regular tests. If this argument is not specified, we only log the serious messages to stderr, which matches the existing behaviour. Reviewers: tfiala, tberghammer Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D16858 llvm-svn: 259774
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/scope/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud