[Top][All Lists]

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

Re: Why does close_stdout close stdout and stderr?

From: Bernhard Voelker
Subject: Re: Why does close_stdout close stdout and stderr?
Date: Mon, 6 May 2019 21:14:22 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

On 5/6/19 5:47 PM, Florian Weimer wrote:
> * Bernhard Voelker:
>> What is the problem?  I mean if it is use-after-free as mentioned in
>> the first mail, then write() after fflush() without error checking via
>> another fflush() is in the same category, isn't it?
> No, there is no memory corruption involved because stdout and stderr
> remain valid.

IMO that's easier to detect than a write() without a following error
checking; the consequences may also be quite fatal for the user.

Have a nice day,

reply via email to

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