[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: `message' not outputting the newline "atomically"

From: Daniele Nicolodi
Subject: Re: `message' not outputting the newline "atomically"
Date: Mon, 1 Jul 2019 19:03:46 +0200
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.7.2

On 01/07/2019 08:39, Eli Zaretskii wrote:
> Emacs is on many platforms a multithreaded program, so it could crash
> or be killed at an un-opportune moment even if the data it processes
> for the current stderr printout in the main thread is itself
> completely valid, let alone if Emacs is in trouble in its main thread
> and some of its data is corrupted.  Thus, the situations where the
> buffering _will_ affect diagnostics are real, not illusory, and the
> desire to avoid losing what little diagnostics we have in these cases
> has nothing to do with religion.
> Once again, the people who decided to make stderr unbuffered were very
> smart.  Over the years, I silently thanked them many times for that
> decision, as I needed to diagnose bugs, both mine and those of others.
> In high-quality software bugs are quite rare, but when they do happen,
> each femto-bit of additional information is precious.  If you don't
> share this basic view, if you think the need for having stderr
> unbuffered needs some proof, then I guess our experiences and/or the
> amounts of gray hair from insufficient diagnostics are very different.

As I already expressed a couple of times now, this is all hypothetical.
The Emacs bug database is vast, can you please explicitly name just one
bug where there was truncated stderr output?

Thank you.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]