From: Jonas Maebe <jonas-devlists@watlock.be>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: gdb on macOS 10.12 "Sierra"
Date: Mon, 31 Oct 2016 11:54:00 -0000 [thread overview]
Message-ID: <581730F0.6000106@watlock.be> (raw)
In-Reply-To: <D32EFDB6-C491-450A-940C-0F5EBA205AE3@adacore.com>
Tristan Gingold wrote:
>> On 01 Oct 2016, at 14:08, Jonas Maebe <jonas-devlists@watlock.be> wrote:
>>
>> Has anyone succeeded yet in getting gdb to work on macOS 10.12? Reportedly, it works when you disable SIP (which is understandable, given https://developer.apple.com/library/content/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html ), but plain code signing no longer seems to cut it.
>
> No, I haven't tried yet. Did you investigate if lldb has updated its build instructions ?
I finally got time to look into this. lldb's codesigning instructions
are at
https://llvm.org/svn/llvm-project/lldb/trunk/docs/code-signing.txt .
They have not been updated recently, but they do differ from gdb's.
However, the result is exactly the same: SIG113.
I've also asked on the darwin-dev@apple list, but did not get any
replies there.
...
I've now tried building lldb, and regardless of whether I use the GDB or
LLDB-style codesigning certificate to sign debugserver (lldb itself does
not need codesigning), it works. So it seems like the problem is not
necessarily related to codesigning per se.
Jonas
next prev parent reply other threads:[~2016-10-31 11:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 12:08 Jonas Maebe
2016-10-04 11:42 ` Tristan Gingold
2016-10-04 13:47 ` Tedeschi, Walfred
2016-10-31 11:54 ` Jonas Maebe [this message]
2016-10-31 12:00 ` Jack Howarth
2016-10-31 12:11 ` Jonas Maebe
2016-10-31 23:24 ` Jason Molenda
2016-11-03 16:00 ` Tristan Gingold
2016-10-31 23:14 C Western
2016-11-03 22:05 David Jenkins
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=581730F0.6000106@watlock.be \
--to=jonas-devlists@watlock.be \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
/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