GDB on Mac OS

Jack Howarth howarth.mailing.lists@gmail.com
Wed Aug 12 14:46:00 GMT 2015


On Wed, Aug 12, 2015 at 10:24 AM,  <Paul_Koning@dell.com> wrote:
>
>> On Aug 12, 2015, at 9:53 AM, Jonas Maebe <jonas.maebe@elis.ugent.be> wrote:
>>
>>
>> Paul_Koning wrote on Wed, 12 Aug 2015:
>>
>>> On Aug 11, 2015, at 11:12 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>>
>>>> - for actual debugging of a live inferior, the debugger needs
>>>>   to be codesigned - try with a simple example first to see
>>>>   if you can run a program and break somewhere.
>>>
>>> So is that the reason why so many tests fail?  I know of the codesigning requirement from actually using the debugger (or rather, answering the prompt for my password, which is the alternative).
>>
>> It's not the alternative, both are required. You won't even get to the password prompt without a codesigned binary.
>
> That’s not what I found.  When I created my signing cert correctly, and signed gdb, it controls the inferior without giving me a developer popup dialog.
>
>>
>>> Where would I look for information on how to do this?
>>
>> https://sourceware.org/gdb/wiki/BuildingOnDarwin
>>
>> In particular also note the addendum regarding taskgated: you also have to add the -p option to that LaunchDaemon plist and reboot before gdb will work for non-root users on OS X 10.9 and 10.10.
>
> From the way I read the Wiki page, the -p option is an alternative (and less desirable) to signing the image.  When I signed it, it worked without the -p.

My experience has been that the -p option is required for full
functionality as non-root users. Without this option gdb will bring up
an authorization dialog for the system password during the 'make
check' of FSF gcc for instance.

>
>         paul



More information about the Gdb mailing list