This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB on Mac OS
- From: <Paul_Koning at Dell dot com>
- To: <jonas dot maebe at elis dot ugent dot be>
- Cc: <gdb at sourceware dot org>
- Date: Wed, 12 Aug 2015 14:24:24 +0000
- Subject: Re: GDB on Mac OS
- Authentication-results: sourceware.org; auth=none
- References: <1739A299-ACE9-4D7F-A1DF-E64C89ECC8D1 at dell dot com> <20150812031208 dot GJ22225 at adacore dot com> <95D02D49-26D2-454E-8E11-70EBF7CB5EC5 at dell dot com> <20150812155327 dot Horde dot J5pTYkisJlFVy0-XHAMRMSA at mail dot elis dot ugent dot be>
> 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.
paul