- Troubleshooting / further diagnosis
- Notes for older versions
If you try to use your freshly built gdb, you might get an error message such as:
Starting program: /x/y/foo Unable to find Mach task port for process-id 28885: (os/kern) failure (0x5). (please check gdb is codesigned - see taskgated(8))
This is because modern Darwin kernels restrict the capability to assume control over another process (here, for the purpose of debugging it), since that capability is a boon to malware. In order for said taskgated to grant access to gdb, the latter must be fitted with entitlements, which consist of digitally-signed metadata inside the gdb binary.
These instructions apply to Mac OS versions 10.14 (Mojave) thru 11.x (Big Sur). See below#Notes_for_older_versions for older versions of Mac OS X.
security find-certificate -c gdb-cert |grep System.keychain
security dump-trust-settings -d
codesign -vv $(which gdb)
None known (besides checking that your gdb now works)
Try gdb again
Still no luck? See Troubleshooting
1.1. Create a certificate in the System Keychain
1.1.1. Automated steps
Download and run this script from the conda-forge GDB package. Note: the script creates a certificate named gdb_codesign instead of gdb-cert, so adapt the commands below accordingly.
1.1.2. Manual steps
Start Keychain Access application (/Applications/Utilities/Keychain Access.app)
Open the menu item /Keychain Access/Certificate Assistant/Create a Certificate...
Choose a name (gdb-cert in the example), set Identity Type to Self Signed Root, set Certificate Type to Code Signing and select the Let me override defaults. Click several times on Continue until you get to the Specify a Location For The Certificate screen, then set Keychain to System.
💡 If you cannot store the certificate in the System keychain: create it in the login keychain instead, then export it. You can then import it into the System keychain.
Finally, quit the Keychain Access application to refresh the certificate store.
In the terminal type
security find-certificate -c gdb-cert
This should display some details about your newly minted certificate, e.g.
keychain: "/Library/Keychains/System.keychain" version: 256 class: 0x80001000 attributes: "alis"<blob>="gdb-cert" [...]
Make sure that keychain: is the System keychain, as shown.
Also, make sure that your certificate is not expired yet:
security find-certificate -p -c gdb-cert | openssl x509 -checkend 0
💡If you want to inspect the entire X509 data structure, you can type
security find-certificate -p -c gdb-cert |openssl x509 -noout -text
1.2. Trust the certificate for code signing
1.2.1. Automated steps
The certificate created by the macos-setup-codesign.sh script mentioned in the previous section is already correctly set up.
1.2.2. Manual steps
Start Keychain Access again. Using the contextual menu for the certificate, select Get Info, open the Trust item, and set Code Signing to Always Trust.
Finally, quit the Keychain Access application once more to refresh the certificate store.
In the terminal type
security dump-trust-settings -d
This should show the gdb-cert certificate (perhaps among others) and its trust settings, including Code Signing.
1.3. Sign and entitle the gdb binary
Create a gdb-entitlement.xml file containing the following:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>com.apple.security.cs.debugger</key> <true/> </dict> </plist>
If the certificate you generated in the previous section is known as gdb-cert, use:
codesign --entitlements gdb-entitlement.xml -fs gdb-cert $(which gdb)
💡 You may have to prepend this command with sudo if the gdb binary is located in a place that is not writable by regular users.
If you plan to build gdb frequently, this step can be automated by passing --enable-codesign=gdb-cert (assuming, again, that gdb-cert is the name of the certificate) to configure.
Control: in the terminal type
codesign -vv $(which gdb) codesign -d --entitlements :- $(which gdb)
1.4. Refresh the system's certificates and code-signing data
The most reliable way is to reboot your system.
A less invasive way is to and restart taskgated service by killing the current running taskgated process (at any time in the process, but no later than before trying to run gdb again):
sudo killall taskgated
However, sometimes the taskgated service will not restart successfully after killing it, so ensure that it is alive after this step by checking e.g. ps $(pgrep -f taskgated). Or just reboot your system, as mentioned above.
2. Troubleshooting / further diagnosis
⚠ There is plenty of other reasons why gdb might not work on Darwin, besides it not being code-signed with the com.apple.security.cs.debugger entitlement.
gdb does not understand “fat” binaries at the moment. You may have to preprocess the target binary with lipo -thin x86_64
If gdb launches the process, but then hangs, you might be running into bug #24069. Keep trying again until the debugger starts successfully, or apply the suggested patch and rebuild gdb.
If, on the other hand you still get the (os/kern) failure (0x5) error, one of the following suggestions may pinpoint you to the cause.
If you are trying to attach to a running program using gdb's attach command, then that program (the target one, not gdb) must have the com.apple.security.get-task-allow entitlement set (in addition to gdb's own entitlement). You can achieve that with codesign using the same instructions and certificate you already used to sign gdb — Just change the entitlement name inside the XML plist file accordingly.
Double-check all commands in the checklist and redo the corresponding step in case of trouble
You may have also (partly) followed the instructions from the old method section. E.g., if the gdb binary is setgid procmod, the code-signing method will not work anymore. In that case, restore the gdb binary to the original settings with the following commands:
$ chmod 755 gdb $ chgrp admin gdb
(possibly prepended with sudo if the gdb binary is located in a place that cannot be modified by regular users or if you do not belong to the admin group, and replacing gdb with the full path to the gdb binary)
Ensure that you code-signed the actual gdb binary and not just a script that starts this binary (you can code-sign shell scripts too). Check using e.g. the file command that the file you code-signed is a binary and not a text file or shell script.
2.1. Watch Logs
The following command will stream the log messages pertaining to taskgated and code-signing issues:
log stream --predicate 'process = "taskgated" OR (process = "kernel" AND eventMessage CONTAINS "macOSTaskPolicy")' --info
3. Notes for older versions
3.1. High Sierra (10.13)
3.2. Leopard (10.5) thru High Sierra (10.13)
These versions do not have entitlement metadata; just signing the gdb binary was enough to make it work. In that case, the codesign command to use is just
codesign -fs gdb-cert $(which gdb)
Accordingly, all checks based on codesign -d --entitlements won't work, so just skip them.
3.3. Tiger (10.4) and before
Warning: do not combine (part of) these instructions with the code signing method, because they interfere with each other. In general, following the instructions in this section is strongly discouraged.
In Mac OS X 10.4 (Tiger), the kernel would let processes whose primary effective group is procmod or procview act as debuggers. That means that making gdb setgid procmod worked.
Later versions of Darwin still accept this convention provided that taskgated (the daemon that controls the access) is invoked with option '-p'. This daemon is configured by /System/Library/LaunchDaemons/com.apple.taskgated.plist, which is where you can add this '-p' option. On OS X 10.11 (El Capitan) and later, this requires (temporarily) disabling rootless mode, otherwise that file cannot be modified.
On OS X 10.10 (Yosemite) and later, you also need to be a member of the Unix group _developer for this method to work. In case your use name is Jack, you can do this with the following command:
$ sudo dscl . merge /Groups/_developer GroupMembership Jack
Follow the instructions above to refresh all subsystems that need to know about this group change.