Kernel dies when debugger is attached

[ihnorton]

The kernel stops responding when lldb is attached to the Slicer process on macOS. Slicer prints the following in the notebook terminal, and in a popup window:

"Slicer has caught an internal error.\n\nYou may be able to continue from this point, but results are undefined.\n\nSuggested action is to save your work and restart.\n\nIf you have a repeatable sequence of steps that causes this message, please report the issue following instructions available at http://slicer.org\n\n\nThe message detail is:\n\nException thrown in event: Interrupted system call"

[ihnorton]

Partially fixed by #4: the internal error message is still displayed (when the debugger attaches, and every time a breakpoint is set), but the kernel keeps responding, and the debugger stops at breakpoints as expected.

[lassoan]

FYI, all debuggers (both Python and native C++) work without any problems on Windows.

[lassoan]

I think this issue has been fixed (no user reported this error recently).