public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Add --enable-codesign to gdb's configure
Date: Thu, 28 Jun 2018 19:20:00 -0000	[thread overview]
Message-ID: <20180628192051.GD2511@adacore.com> (raw)
In-Reply-To: <83zhzeoja4.fsf@gnu.org>

Hi Eli,

> OK for the NEWS part, but I think we should reflect this option in the
> output of "gdb --configure", because users will want to know whether
> their GDB was configured that way.

The new option actually influences the build, not whether GDB provides
a given feature or not.

On MacOS X, GDB needs to be codesigned in order to be allowed debug
privileges. What Tom's configuration option does is that it automates
that during the build so that it gets automatically done each time
the user types "make". Users who do not use the new option already
achieve the same effect by running the codesign command by hand
each time after running "make".

If a user wants to know whether his binary has been codesigned or
not, and if yes, using which certificate, he can also use the codesign
command.
http://osxdaily.com/2016/03/14/verify-code-sign-apps-mac-os-x/

-- 
Joel

  reply	other threads:[~2018-06-28 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 16:37 Tom Tromey
2018-06-28 17:31 ` Joel Brobecker
2018-06-28 18:31 ` Eli Zaretskii
2018-06-28 19:20   ` Joel Brobecker [this message]
2018-06-28 21:12     ` Tom Tromey
2018-06-29 22:19       ` Joel Brobecker

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=20180628192051.GD2511@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).