This commit allows you to control the signals that lldb will suppress, stop or forward using the Python and C++ APIs.
I've tested it on Ubuntu 12.04 cmake/ninja, and (with adjustments to build file) MacOSX 10.9.3/Xcode 6 beta.
Linux x86_64 local test suite is running complete and passing.
New test is running on MacOSX without error.
Transmitting file data ............
Committed revision 211526.
Transmitting file data ...
Committed revision 211535.
That's the test methods that were missing. Ed Maste caught the .i file before I got to it.
This breaks the windows build. The name of this file suggests that it's
platform specific, but none of the code in particular that it's using is
actually platform specific. Should this file be compiled on Windows or not?
It should be just as platform dependant as the UnixSignals object it relies
on. I didn't originally write it with windows in mind.
What's standard procedure here? Rollback? Or fix forward?
Without looking at the code, how does Windows deal with the UnixSignals
object? Is it just not built?
Thanks. It looks like UnixSignals.cpp is compiled on Windows, therefore
this should too. For whatever reason, the list of files to compile for the
API are maintained in a different CMake location on Windows than on
non-Windows. So when adding a file to API, you need to add it in two
places. Don't revert, I'll just check in a fix that compiles on Windows.
Already tested it locally, just wanted to confirm your intent first.