From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: henrik@grimler.se, 47596@debbugs.gnu.org
Subject: bug#47596: File descriptor error when exiting emacs on android 11
Date: Wed, 12 May 2021 17:01:36 +0300 [thread overview]
Message-ID: <83r1ic2gqn.fsf@gnu.org> (raw)
In-Reply-To: <87mtt0jbyj.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 12 May 2021 15:52:52 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: eliz@gnu.org, 47596@debbugs.gnu.org
> Date: Wed, 12 May 2021 15:52:52 +0200
>
> Henrik Grimler <henrik@grimler.se> writes:
>
> > Could this work or do we need to have both buferr and stderr?
>
> Makes sense to me, but I seem to vaguely recall there being a lot of
> discussion about the buffered stderr when it was introduced... but none
> of the details. Eli?
We need them both, yes. The second one was introduced for a reason,
so removing it would give us back the problems it solved.
setlinebuf is not portable enough, and line buffering isn't supported
on MS-Windows anyway. Maybe we could make some archlinux specific
change, although that's ugly.
And I'm worried that we don't actually understand the nature of the
problem well enough: our code doesn't close both FILE streams, it
closes at most only one. So this sounds to me like a false positive
of the sanitizer, not a real problem with our code...
next prev parent reply other threads:[~2021-05-12 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 19:20 bug#47596: File descriptor error when exiting emacs on android 11 Henrik Grimler
2021-04-04 19:31 ` Eli Zaretskii
2021-04-04 20:11 ` Henrik Grimler
2021-04-05 8:14 ` Henrik Grimler
2021-04-05 8:59 ` Henrik Grimler
2021-04-05 9:48 ` Henrik Grimler
2021-04-05 12:57 ` Eli Zaretskii
2021-04-05 13:38 ` Henrik Grimler
2021-04-05 12:52 ` Eli Zaretskii
2021-04-05 12:50 ` Eli Zaretskii
2021-04-05 17:29 ` Henrik Grimler
2021-05-06 10:45 ` Lars Ingebrigtsen
2021-05-10 7:23 ` Henrik Grimler
2021-05-11 17:06 ` Henrik Grimler
2021-05-12 13:52 ` Lars Ingebrigtsen
2021-05-12 14:01 ` Eli Zaretskii [this message]
2022-06-29 10:47 ` Lars Ingebrigtsen
2022-06-29 13:25 ` Henrik Grimler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-30 9:07 ` Lars Ingebrigtsen
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=83r1ic2gqn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47596@debbugs.gnu.org \
--cc=henrik@grimler.se \
--cc=larsi@gnus.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.
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).