#C debugger for mac sierra code#

The hardened runtime capability is available in Xcode 10.0 and later on macOS v10.3.6 and later. Xcode 10 has shipped with another strange new feature, called the 'hardened runtime'. It would be nice if Apple communicated and documented this information clearly instead of leaving developers in the dark and fumbling around for answers, like I'm doing here. Thus, the situation is not quite as bad as feared.

After you authenticate with DevToolsSecurity once, Developer Mode is permanently enabled on Mojave, and you won't have to authenticate again to debug. However, Developer Mode can still be enabled manually with /usr/sbin/DevToolsSecurity -enable in Terminal. On Mojave, Xcode no longer requests Developer Mode. Prior to Mojave, Xcode would request on first launch to 'Enable Developer Mode on this Mac'. UpdateĪfter writing this blog post, I discovered why you have to authenticate again after logout. If you do logout and login again, the system will start asking again for permission the next time you try to debug. Eventually it gives up after 10 cancels.) If you successfully authenticate once, then it appears that you can continue to debug other apps without further system requests, as long as you don't logout. (By the way, pressing the Cancel button just causes the system to ask you again, instead of canceling. Unless you authenticate, you can't debug the app. This happens whether or not you have System Integrity Protection enabled! SIP status doesn't matter here. On Mojave, however, the first time after login that you try to debug an app without the -task-allow entitlement, the system displays a modal dialog requesting an administrator password:ĭeveloper Tool Access needs to take control of another process for debugging to continue. The process launches and then stops at the breakpoint, most likely in CoreFoundation`. On High Sierra, 'it just works', as they say. (lldb) target create '/Applications/Underpass.app/Contents/MacOS/Underpass'Ĭurrent executable set to '/Applications/Underpass.app/Contents/MacOS/Underpass' (x86_64). Here's a sample of a debugging session in Terminal: $ lldb /Applications/Underpass.app/Contents/MacOS/Underpass We can confirm with codesign -d -entitlements - /Applications/Underpass.app that the -task-allow entitlement does not exist in the App Store version. To test, I tried debugging my own app Underpass installed from the Mac App Store. Apps won't have the entitlement if you didn't build them yourself, or if you exported them for distribution from Xcode.

The situation has changed for apps that lack the -task-allow entitlement. You can see the -task-allow entitlement, which allows you to debug the app either in Xcode or with /usr/bin/lldb in Terminal.

#C debugger for mac sierra code#

Examine the code signature of your built app: $ codesign -d -entitlements - MyApp.app There are indeed some changes to debugging on Mojave, and this blog post will describe what I've discovered so far.ĭebugging apps in your Xcode build folder has not changed on Mojave. In retrospect, it appears that the words were a bit premature - a leak, if you will - and 'macOS now requires' referred to macOS 10.14 Mojave, still secret at the time, rather than macOS 10.13 High Sierra. The entitlement is stripped from apps distributed using the Organizer window.Īt the time, this note caused some confusion and anxiety. Xcode automatically injects this entitlement to your builds. The debugger on macOS now requires the entitlement -task-allow to attach to apps built for macOS or for iOS, tvOS or watchOS apps built for Simulator. The Xcode Release Notes miscategorized the feature under the 'Server' section: In March, Xcode 9.3 shipped with a strange new feature. Articles index Debugging on Mojave JBy Jeff Johnson (Developer of StopTheMadness and Underpass)