From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [RFC 0/6] A different approach to startup-with-shell on macOS
Date: Wed, 26 Sep 2018 11:12:00 -0000 [thread overview]
Message-ID: <20180926111130.18956-1-tom@tromey.com> (raw)
Currently the macOS port will disable startup-with-shell on versions
of macOS that have System Integrity Protection. This is done because
with SIP, gdb cannot ptrace certain executables, including the normal
shells.
This series implements a different approach: copy the user's shell
executable to the cache directory and arrange to use the copy. This
avoids the SIP restrictions.
Most of the series is just cleanup, rearranging so some private
functions can be shared, and fixing a few small things I noticed along
the way.
This has been regression tested by one of the buildbot builders, and
then I tested the final patch on macOS High Sierra.
One question I have is whether it's possible to build gdb on an older
version of macOS and then run it on a newer version. If this can be
done, then the #if-based approach taken in the final patch will not
work.
I didn't include any way to control this feature other than "set
startup-with-shell off". My thinking was that turning this off will
just result in failures, which isn't useful. However if there's a
reason to do something else, I could add it.
Tom
next reply other threads:[~2018-09-26 11:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 11:12 Tom Tromey [this message]
2018-09-26 11:11 ` [RFC 1/6] Unify shell-finding logic Tom Tromey
2018-09-28 21:39 ` Simon Marchi
2018-09-26 11:12 ` [RFC 5/6] Do not reopen temporary files Tom Tromey
2018-09-26 14:12 ` Eli Zaretskii
2018-09-26 21:44 ` Tom Tromey
2018-09-29 3:22 ` Simon Marchi
2018-10-01 9:15 ` Tom Tromey
2018-09-26 11:12 ` [RFC 2/6] Move make_temp_filename to common/pathstuff.c Tom Tromey
2018-09-26 11:12 ` [RFC 4/6] Use mkostemp, not mkstemp Tom Tromey
2018-09-29 3:09 ` Simon Marchi
2018-09-29 12:49 ` Tom Tromey
2018-09-29 14:04 ` Simon Marchi
2018-09-26 11:20 ` [RFC 3/6] Move mkdir_recursive to common/filestuff.c Tom Tromey
2018-09-26 22:11 ` Tom Tromey
2018-09-26 23:16 ` Tom Tromey
2018-09-26 11:20 ` [RFC 6/6] Cache a copy of the user's shell on macOS Tom Tromey
2018-09-29 3:37 ` Simon Marchi
2018-10-01 19:27 ` Tom Tromey
2018-10-01 19:31 ` Simon Marchi
2018-09-28 21:21 ` [RFC 0/6] A different approach to startup-with-shell " Simon Marchi
2018-09-29 18:43 ` Pedro Alves
2018-09-29 19:50 ` Simon Marchi
2018-09-29 20:38 ` Pedro Alves
2018-10-01 9:12 ` 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=20180926111130.18956-1-tom@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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