diff options
| author | Shawn Best <sbest@blueshiftinc.com> | 2014-11-21 06:49:39 +0000 |
|---|---|---|
| committer | Shawn Best <sbest@blueshiftinc.com> | 2014-11-21 06:49:39 +0000 |
| commit | d64bc4bee6eab912b3a02ab9cab13f13045ba0ea (patch) | |
| tree | bd9c6db31c48f8e031d908fbbed4bf0f55eda0af /lldb/scripts/Python/finishSwigPythonLLDB.py | |
| parent | 44e5d7a131d300ce6ba023551e3658e714db0a5a (diff) | |
| download | bcm5719-llvm-d64bc4bee6eab912b3a02ab9cab13f13045ba0ea.tar.gz bcm5719-llvm-d64bc4bee6eab912b3a02ab9cab13f13045ba0ea.zip | |
fix Bug21211 : reworked test/api/multithreaded/test_listener_event_description.cpp to work properly on Linux/FreeBSD
Issue D5632 fixed an issue where linux would dump spurious output to tty on startup (due to a broadcast stop event). After the checkin, it was noticed on FreeBSD a unit test was now failing. On closer investigation I found the test was using the C++ API to launch an inferior while using an SBListener to monitor the public state changes. As on OSx, it was expecting to see:
eStateRunning
eStateStopped
On Linux/FreeBSD, there is an extra state change
eStateLaunching
eStateRunning
eStateStopped
I reworked the test to work for both cases and re-enabled the test of FreeBSD.
Differential Revision: http://reviews.llvm.org/D5837
llvm-svn: 222511
Diffstat (limited to 'lldb/scripts/Python/finishSwigPythonLLDB.py')
0 files changed, 0 insertions, 0 deletions
