> On Oct 11, 2016, at 2:26 PM, Ronald Oussoren <ronaldousso...@mac.com> wrote: > > BTW. Has anyone experience with using LLDB on Sierra? I’m currently running > Sierra in a VM and for some reason LLDB doesn’t appear to work, in an SSH > session I cannot start programs at all and on the console a crashing bug in > the interpreter exists the interpreter instead of breaking into the debugger. > That’s rather annoying when you’re trying to a debug a crash on 10.12 that > doesn’t happen on 10.11.
Ever since the introduction of SIP, system-level debugging tools like LLDB have worked very poorly for me, even on self-built executables. I don't see a difference in its behavior on 10.11 vs. 10.12 though. I can run it on `curl` from Homebrew, but not `python`; my guess being that Python is trying to dlopen() some SIP-protected thing whereas `curl` is loading only things from Homebrew? If it's a VM, then system integrity is less of a concern; have you tried just blanket disabling SIP to see if that improves the situation? I've had some luck with other tools (dtrace, mostly) working in that configuration. (I had to totally disable SIP though, disabling one flag at a time didn't work.) -glyph
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
