From: Joel Brobecker <brobecker@adacore.com>
To: Adrian Ho <co+sourceware@03s.net>
Cc: gdb@sourceware.org
Subject: Re: Outdated entitlement instructions on GDB WIki
Date: Tue, 18 Aug 2020 09:39:38 -0700 [thread overview]
Message-ID: <20200818163938.GB17414@adacore.com> (raw)
In-Reply-To: <3663aeba-5cca-5049-d193-c1aeafcfddb8@03s.net>
Hi Adrian,
> I've tested and verified that the single entitlement documented in 1.3.1. of
> https://sourceware.org/gdb/wiki/PermissionsDarwin is insufficient for macOS
> Catalina at least, and possibly even for Mojave.
>
> Instead, I've had to use an expanded set of entitlements documented at https://www.thomasvitale.com/how-to-setup-gdb-and-eclipse-to-debug-c-files-on-macos-sierra/,
> i.e.:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
> "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
> <plist version="1.0">
> <dict>
> <key>com.apple.security.cs.allow-jit</key>
> <true/>
> <key>com.apple.security.cs.allow-unsigned-executable-memory</key>
> <true/>
> <key>com.apple.security.cs.allow-dyld-environment-variables</key>
> <true/>
> <key>com.apple.security.cs.disable-library-validation</key>
> <true/>
> <key>com.apple.security.cs.disable-executable-page-protection</key>
> <true/>
> <key>com.apple.security.cs.debugger</key>
> <true/>
> <key>com.apple.security.get-task-allow</key>
> <true/>
> </dict>
> </plist>
>
> Appreciate it if someone could update the above wiki page, as I'm not
> permitted to do it myself. Thanks much!
I think this is better done by someone who has actual experience
on MacOS X. Would you be willing to perform the update, if we gave
you write access to the Wiki? All you have to do is create an account,
and then send me your ID (you can send it to me privately), and I will
add you.
--
Joel
next prev parent reply other threads:[~2020-08-18 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 11:18 Adrian Ho
2020-08-18 16:39 ` Joel Brobecker [this message]
2020-08-21 15:54 ` Tom Tromey
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=20200818163938.GB17414@adacore.com \
--to=brobecker@adacore.com \
--cc=co+sourceware@03s.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).