How to get a “codesigned” gdb on OSX?

by

I.1 Codesigning the Debugger

The Darwin Kernel requires the debugger to have special permissions
before it is allowed to control other processes. These permissions are
granted by codesigning the GDB executable. Without these permissions,
the debugger will report error messages 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))

Codesigning requires a certificate. The following procedure explains how to create one:

  • Start the Keychain Access application (in /Applications/Utilities/Keychain Access.app)
  • Select the Keychain
    Access -> Certificate Assistant -> Create a Certificate… menu
  • Then:
    • Choose a name for the new certificate (this procedure will use
      “gdb-cert” as an example)
    • Set “Identity Type” to “Self Signed Root”
    • Set “Certificate Type” to “Code Signing”
    • Activate the “Let me override defaults” option
  • Click several times on “Continue” until the “Specify
    a Location For The Certificate” screen appears, then set “Keychain” to “System”
  • Click on “Continue” until the certificate is created
  • Finally, in the view, double-click on the new certificate, and set “When using
    this certificate” to “Always Trust”
  • Exit the Keychain Access application and restart the computer (this is unfortunately required)

Once a certificate has been created, the debugger can be codesigned as
follow. In a Terminal, run the following command…

codesign -f -s  "gdb-cert"  <gnat_install_prefix>/bin/gdb

… where “gdb-cert” should be replaced by the actual certificate name
chosen above, and should be replaced by the
location where you installed GNAT.

source: https://gcc.gnu.org/onlinedocs/gcc-4.8.1/gnat_ugn_unw/Codesigning-the-Debugger.html

UPDATE: High-Sierra (Certificate Assistant – Unknown Error)
https://apple.stackexchange.com/questions/309017/unknown-error-2-147-414-007-on-creating-certificate-with-certificate-assist

More Related Contents:

  1. Can I set a breakpoint on ‘memory access’ in GDB?
  2. Debugging core files generated on a Customer’s box
  3. How do I print the elements of a C++ vector in GDB?
  4. Run an Application in GDB Until an Exception Occurs
  5. How do I print the full value of a long string in gdb?
  6. How to pretty-print STL containers in GDB?
  7. How to set a breakpoint in GDB where the function returns?
  8. How do I use the MinGW gdb debugger to debug a C++ program in Windows?
  9. How to pass arguments and redirect stdin from a file to program run in gdb?
  10. “please check gdb is codesigned – see taskgated(8)” – How to get gdb installed with homebrew code signed?
  11. How to avoid entering library’s source files while debugging in Qt Creator with gdb?
  12. How do I see a C/C++ source file after preprocessing in Visual Studio?
  13. Finding current executable’s path without /proc/self/exe
  14. How to create minidump for my process when it crashes?
  15. How can I tell if a library was compiled with -g?
  16. Determine Process Info Programmatically in Darwin/OSX
  17. Qt Creator – Project ERROR: Xcode not set up properly. You may need to confirm the license agreement by running /usr/bin/xcodebuild
  18. Simulating key press events in Mac OS X
  19. Is there any way to set a breakpoint in gdb that is conditional on the call stack?
  20. Critique my non-intrusive heap debugger
  21. Stopping the debugger when a NaN floating point number is produced
  22. How to use Libraries
  23. Broken c++ std libraries on macOS High Sierra 10.13
  24. traceback a pointer in c++ code gdb
  25. Missing C++ header after updating OSX Command Line Tools 6.3
  26. gdb Could not find operator[]
  27. Default libraries linked in by gcc?
  28. Where can I get windows.h for Mac?
  29. C++ GDB Python Pretty Printing Tutorial?
  30. “Step over” when debugging multithreaded programs in Visual Studio

Leave a Comment