From: Robert Pluim <rpluim@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: gerd.moellmann@gmail.com, 58960@debbugs.gnu.org,
Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#58960: 29.0.50; Assert fails when browsing an URL, bug#58960: 29.0.50; Assert fails when browsing an URL
Date: Thu, 03 Nov 2022 09:41:20 +0100 [thread overview]
Message-ID: <87v8nwmnv3.fsf@gmail.com> (raw)
In-Reply-To: <67234859-6953-752-4298-a75cf13f14f8@gmail.com> (Tino Calancha's message of "Thu, 3 Nov 2022 04:00:26 +0100 (CET)")
>>>>> On Thu, 3 Nov 2022 04:00:26 +0100 (CET), Tino Calancha <tino.calancha@gmail.com> said:
Tino> On Wed, 2 Nov 2022, Paul Eggert wrote:
>> child_signal_init is reasonably heavyweight in that it keeps a
>> couple of file descriptors open, so the idea is to be lazy and not
>> call it unless Emacs plans to have children.
>>
Sure. Calling it from `init_process_emacs' works as well, but then
thereʼs some scary looking "if (!will_dump_with_unexec_p ())", so
letʼs not go there :-)
>> I installed the attached, which is like Robert's patch except it
>> keeps the critical section smaller and checks the declaration of the
>> now-extern function. Please give it a try. I'll boldly close the bug
>> report; we can reopen it if I'm wrong.
Tino> I have applied your patch; it fixes the issue.
Tino> Thank you.
Works for me as well, thanks Paul
Robert
--
prev parent reply other threads:[~2022-11-03 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 4:48 bug#58960: 29.0.50; Assert fails when browsing an URL Tino Calancha
2022-11-02 5:14 ` Gerd Möllmann
2022-11-02 10:20 ` bug#58960: 29.0.50; Assert fails when browsing an URL, " Robert Pluim
2022-11-02 13:10 ` Eli Zaretskii
2022-11-02 13:58 ` Robert Pluim
2022-11-02 15:09 ` Eli Zaretskii
2022-11-02 20:29 ` Paul Eggert
2022-11-03 3:00 ` Tino Calancha
2022-11-03 8:41 ` Robert Pluim [this message]
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=87v8nwmnv3.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=58960@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=tino.calancha@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.