GNU logs - #54677, boring messages

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#54677: Creating core files on macOS (Monterey)
Resent-From: Perry Smith <pedz@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Sat, 02 Apr 2022 01:31:02 +0000
Resent-Message-ID: <handler.54677.B.164886301127212 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 54677 <at> debbugs.gnu.org
From: Perry Smith <pedz@HIDDEN>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Message-Id: <1DAC996D-BBF6-4E3E-A0FB-EBD05CC9AFD2@HIDDEN>
Date: Fri, 1 Apr 2022 18:54:56 -0500
Received-SPF: pass client-ip=23.83.212.17; envelope-from=pedz@HIDDEN;
 helo=bird.elm.relay.mailchannels.net
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.3 (-)
X-Mailman-Approved-At: Fri, 01 Apr 2022 21:30:10 -0400
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.3 (--)

The CONTRIBUTE document says to submit feature requests, etc to this
list.

I wish I could provide more expertise on this topic but I=E2=80=99m not =
a
serious macOS developer.  I've cobbled together the info below over
the past few days.

Apple (like AIX) has decided that core files are bad and so has
disabled them in the normal activities.  So, a few things need to be
done to get a core file from a particular applicaiton.

Another Apple trait seems to be that if they did it yesterday, it must
be changed for today.  Thus, what follows is ONLY for Monterey (I've
been told).  The previous Apple releases require some but not all of
these changes.  AND... it appears that what is required for the M1
chips (Arm / Apple silicon) is not the same as what is required for
Intel chips.  So... I know that without these changes core dumps on
Monterey with an M1 chip were not created and after these changes they
are.

As I mentioned in an email on the developers list, making emacs
remains a drop dead easy process where

./configure ; make ; make install

creates nextstep/Emacs.app

ls -ld@ nextstep/Emacs.app

shows:

drwxr-xr-x@ 3 pedz  staff  96 Apr  1 18:08 nextstep/Emacs.app
	com.apple.quarantine	57=20

To get the Emacs.app to launch, the quarantine needs to be removed and
that is done with:

sudo xattr -rds com.apple.quarantine nextstep/Emacs.app

The app can then be moved to /Applications and it will launch via
Finder, etc but will not create a core file.

To get an application to create a core file two particular things need
to be done.  The resource limit for core files needs to be set to the
max.  And an entitlement needs to be applied to the application.

The first I accomplished with this code change:

diff -r emacs-orig-27.2/src/emacs.c emacs-new-27.2/src/emacs.c
1226c1226,1234
<=20
---
> #if defined (HAVE_SETRLIMIT) && defined (RLIMIT_CORE) && !defined =
(CYGWIN)
>   if (getrlimit (RLIMIT_CORE, &rlim) =3D=3D 0
>       && 0 <=3D rlim.rlim_cur && rlim.rlim_cur <=3D rlim.rlim_max)
>     {
>       rlim.rlim_cur =3D rlim.rlim_max;
>       setrlimit (RLIMIT_CORE, &rlim); /* Error??? */
>     } =20
> #endif /* HAVE_SETRLIMIT and RLIMIT_CORE and not CYGWIN */
>  =20

The second I accomplished with this small script:

#!/bin/zsh

EMACS=3D/Applications/Emacs.app
if [[ -d nextstep/Emacs.app ]] ; then
  sudo rm -rf ${EMACS}
  sudo mv nextstep/Emacs.app ${EMACS}
  rm -f /tmp/entitlements
  /usr/libexec/PlistBuddy -c "Add :com.apple.security.get-task-allow =
bool true" /tmp/entitlements
  sudo codesign -s - -f --deep --entitlements tmp.entitlements ${EMACS}
else
  echo nextstep/Emacs.app is not present
fi

The PlistBuddy command will spew out a message:

File Doesn't Exist, Will Create: /tmp/entitlements

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: Perry Smith <pedz@HIDDEN>
Subject: bug#54677: Acknowledgement (Creating core files on macOS (Monterey))
Message-ID: <handler.54677.B.164886301127212.ack <at> debbugs.gnu.org>
References: <1DAC996D-BBF6-4E3E-A0FB-EBD05CC9AFD2@HIDDEN>
X-Gnu-PR-Message: ack 54677
X-Gnu-PR-Package: emacs
Reply-To: 54677 <at> debbugs.gnu.org
Date: Sat, 02 Apr 2022 01:31:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@HIDDEN

If you wish to submit further information on this problem, please
send it to 54677 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
54677: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D54677
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-gnu-emacs@HIDDEN:

Subject: bug#54677: Creating core files on macOS (Monterey)
Resent-From: Lars Ingebrigtsen <larsi@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-gnu-emacs@HIDDEN
Resent-Date: Sat, 02 Apr 2022 14:17:01 +0000
Resent-Message-ID: <handler.54677.B54677.16489090036048 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: Perry Smith <pedz@HIDDEN>
Cc: Alan Third <alan@HIDDEN>, 54677 <at> debbugs.gnu.org
From: Lars Ingebrigtsen <larsi@HIDDEN>
References: <1DAC996D-BBF6-4E3E-A0FB-EBD05CC9AFD2@HIDDEN>
Date: Sat, 02 Apr 2022 16:16:31 +0200
In-Reply-To: <1DAC996D-BBF6-4E3E-A0FB-EBD05CC9AFD2@HIDDEN> (Perry
 Smith's message of "Fri, 1 Apr 2022 18:54:56 -0500")
Message-ID: <87fsmvk1ts.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Perry Smith <pedz@HIDDEN> writes:

> As I mentioned in an email on the developers list, making emacs
> remains a drop dead easy process where
>
> ./configure ; make ; make install

Note that you don't have to say "make install" -- you can just run it
from src/emacs in the build directory (and that's usually a lot more
convenient when building things yourself).

> To get the Emacs.app to launch, the quarantine needs to be removed and
> that is done with:
>
> sudo xattr -rds com.apple.quarantine nextstep/Emacs.app

And then you don't have to do this, for instance.

> To get an application to create a core file two particular things need
> to be done.  The resource limit for core files needs to be set to the
> max.  And an entitlement needs to be applied to the application.
>
> The first I accomplished with this code change:
>
> diff -r emacs-orig-27.2/src/emacs.c emacs-new-27.2/src/emacs.c
> 1226c1226,1234
> < 
> ---
>> #if defined (HAVE_SETRLIMIT) && defined (RLIMIT_CORE) && !defined (CYGWIN)
>>   if (getrlimit (RLIMIT_CORE, &rlim) == 0
>>       && 0 <= rlim.rlim_cur && rlim.rlim_cur <= rlim.rlim_max)
>>     {
>>       rlim.rlim_cur = rlim.rlim_max;
>>       setrlimit (RLIMIT_CORE, &rlim); /* Error??? */
>>     }  
>> #endif /* HAVE_SETRLIMIT and RLIMIT_CORE and not CYGWIN */

Is this necessary when you're not running installed?

I've added Alan to the CCs; perhaps he has some comments.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Last modified: Sat, 2 Apr 2022 14:15:01 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.