Date: Wed, 26 Feb 1997 00:42:13 +1100 From: Bruce Evans <bde@zeta.org.au> To: freebsd-hackers@freefall.freebsd.org, nao@sbl.cl.nec.co.jp Subject: Re: MALLOC(3) writes to stderr... Message-ID: <199702251342.AAA10884@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>How should we deal with this anomaly? Yep, fixing jserver's memory >allocation thoroughly might be the ultimate solution, but we need a >practical solution for now. Must we change jserver to keep stderr open >and to put error messages into /var/log/jserver.log or something? Or >make malloc(3) keep silent? Library routines shouldn't write to std* unless instructed to. There should be a malloc option to control the behaviour. However, malloc() only seems to print to stderr after severe errors that might have caused a core dump on other systems. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702251342.AAA10884>