Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: gdb@sourceware.org
Subject: Re: GDB on Mac OS
Date: Wed, 12 Aug 2015 13:53:00 -0000	[thread overview]
Message-ID: <20150812155327.Horde.J5pTYkisJlFVy0-XHAMRMSA@mail.elis.ugent.be> (raw)
In-Reply-To: <95D02D49-26D2-454E-8E11-70EBF7CB5EC5@dell.com>


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.

> 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.


Jonas


  reply	other threads:[~2015-08-12 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  0:15 Paul_Koning
     [not found] ` <20150812031208.GJ22225@adacore.com>
2015-08-12 13:38   ` Paul_Koning
2015-08-12 13:53     ` Jonas Maebe [this message]
2015-08-12 13:59     ` Joel Brobecker
2015-08-12 14:06       ` Paul_Koning
2015-08-12 15:14         ` Joel Brobecker
2015-08-12 15:35           ` Stan Shebs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150812155327.Horde.J5pTYkisJlFVy0-XHAMRMSA@mail.elis.ugent.be \
    --to=jonas.maebe@elis.ugent.be \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox