On 5/6/19 9:19 PM, Florian Weimer wrote: > How would a programmer check that close_stdout has run, to determine > that stdout and stderr are now invalid, to avoid the memory corruption?
lib/closeout.c:98: "Since close_stdout is commonly registered via 'atexit', [...]" close_stdout is used right before the process ends, so I don't see what further actions would follow. It seems to me that you're trying to prevent programming errors. So even the programmer knows his/her code, or maybe he can try some static code analyzers to find this issue. Is there a recent case which fell into this (quite obvious) trap? Have a nice day, Berny
