From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tomekowal@gmail.com, Robert Pluim <rpluim@gmail.com>,
39164@debbugs.gnu.org, jguenther@gmail.com
Subject: bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems
Date: Tue, 28 Jan 2020 19:06:09 +0900 [thread overview]
Message-ID: <wlmua7zyi6.wl-mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <88A26EA5-725A-43D4-9A13-065703B9F9A4@gnu.org>
On Tue, 28 Jan 2020 18:42:29 +0900,
Eli Zaretskii wrote:
>
> On January 28, 2020 11:14:41 AM GMT+02:00, YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> wrote:
> > On Tue, 28 Jan 2020 18:02:52 +0900,
> > Eli Zaretskii wrote:
> > >
> > > I'm not sure I understand the implication. How will this workaround
> > ensure starting a subprocess doesn't produce a file descriptor beyond
> > FD_SETSIZE? Maybe all I'm missing is under what conditions will the
> > code you propose be called.
> >
> > It is called during the Mac terminal initialization.
>
>
> And the increase in the number of available descriptors triggered by the system libraries is guaranteed to be called before that? Then how is this call to setrlimit is dufferent from what we already do at startup?
The increase happens only once per function in question. So we make a
dummy call in advance so later calls may not cause the increase in
unpredicable timings.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2020-01-28 10:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 19:00 bug#39164: 27.0.60; Intermittent crash on MacOS 10.14 in setup_process_coding_systems Justin Guenther
2020-01-17 21:01 ` Eli Zaretskii
2020-01-20 9:15 ` Robert Pluim
2020-01-20 18:00 ` Eli Zaretskii
2020-01-20 18:42 ` Robert Pluim
2020-01-27 13:26 ` mituharu
2020-01-27 18:19 ` Eli Zaretskii
2020-01-28 7:59 ` Robert Pluim
2020-01-28 8:23 ` YAMAMOTO Mitsuharu
2020-01-28 8:41 ` Robert Pluim
2020-01-28 9:02 ` Eli Zaretskii
2020-01-28 9:14 ` YAMAMOTO Mitsuharu
2020-01-28 9:42 ` Eli Zaretskii
2020-01-28 10:06 ` YAMAMOTO Mitsuharu [this message]
2020-01-28 17:37 ` Eli Zaretskii
2020-01-29 10:26 ` YAMAMOTO Mitsuharu
2020-01-29 11:09 ` Eli Zaretskii
2020-01-29 12:38 ` Eli Zaretskii
2020-01-30 9:42 ` YAMAMOTO Mitsuharu
2020-01-30 14:49 ` Eli Zaretskii
2020-01-26 17:41 ` bug#39164: Reproducing SIGSEGV bug Tomasz Kowal
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wlmua7zyi6.wl-mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=39164@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jguenther@gmail.com \
--cc=rpluim@gmail.com \
--cc=tomekowal@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).