There are many topics floating around covering codesign issues with macOS, from 10.5 onward. What I wanted to achieve is, to get Geany working with the GNU Debugger (gdb). Debugger is found in geany, but the (already quite known) error message is:
Error message from debugger back end: Unable to find Mach task port for process-id 39847: (os/kern) failure (0x5).\n (please check gdb is codesigned - see taskgated(8)) Unable to find Mach task port for process-id 39847: (os/kern) failure (0x5).\n (please check gdb is codesigned - see taskgated(8))
Generally there are many restrictions to consider that (should) allow the usage of gdb, e.g. gdb 8.0.1 may work, gdb 8.1 will not work at all - see here, also confirmed in Lazarus Wiki.
0) I created my certificate "gdb-cert" according to the steps covered by various instructions. Example here
1) I followed the steps of codesigning the gdb executable file (source: gdb, and Stackoverflow) which is in my case under
/usr/local/Cellar/gdb/8.0.1/bin/gdb
(note again, there are issues with 8.1 for some languages - pascal too). If you want to make sure that code is signed, go for
$ codesign -vvvv gdb
in the respective directory. Mine is.
2) Make sure that the certificate was actually assigned to be eligible for code signing - it is in my case. It is also trusted - which is necessary.
3) I also tried the other way to get gdb running described above, where the file was edited (please note, that SIP has to be disabled in recovery first!!!!) Modifications only work if csrutil disable
is used in the recovery.
sudo nano /System/Library/LaunchDaemons/com.apple.taskgated.plist
Devastating thing, after this step, no code editor would start up again (!!), until this change is undone (Geany, Atom, Text Editor, MS Visual Studio - all broken after inserting -sp to the file)
4) In some topics I found that debugging will only work if the command csrutil enable --withouth
debug is used in the recovery. This hasn't changed anything.
Eventually I ended up having:
I would greatly appreciate if anyone could confirm this behavior, a solution to this even more :)
Debug from the menu will result in Eclipse complaining that an Error with command: gdb --version has occurred. The problem is caused by Apple switching away from GDB, the GNU debugger, to LLDB, the LLVM debugger, in their Xcode toolchain (along with the transition from GCC to Clang).
Open the Terminal app, Applications > Utilities > Terminal. This guide uses the Terminal throughout, so it's best to leave it open until you have finished all of the steps. If you don't already have gdb on your system, then you'll need to install it.
This is related to codesign entitlements. you must add "com.apple.security.cs.debugger" key in signing process.
for example you must change codesign -fs gdbcert /usr/local/bin/gdb
to codesign --entitlements gdb.xml -fs gdbcert /usr/local/bin/gdb
.
gdb.xml content must something like following code.
<?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 you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With