From owner-freebsd-hackers  Mon Feb 24 23:56:20 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id XAA07103
          for hackers-outgoing; Mon, 24 Feb 1997 23:56:20 -0800 (PST)
Received: from research.gate.nec.co.jp (research.gate.nec.co.jp [202.32.8.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA07052
          for <freebsd-hackers@freefall.freebsd.org>; Mon, 24 Feb 1997 23:55:53 -0800 (PST)
Received: from sbl-gw.sbl.cl.nec.co.jp by research.gate.nec.co.jp (8.8.5+2.7Wbeta5/950912) with ESMTP id QAA10505; Tue, 25 Feb 1997 16:55:49 +0900 (JST)
Received: from sirius.sbl.cl.nec.co.jp by sbl-gw.sbl.cl.nec.co.jp (8.8.5+2.7Wbeta5/3.3W6) with ESMTP
	id QAA08547; Tue, 25 Feb 1997 16:55:47 +0900 (JST)
Received: by sirius.sbl.cl.nec.co.jp (8.7.5+2.6Wbeta6/3.3W6) with UUCP
	id QAA20017; Tue, 25 Feb 1997 16:55:47 +0900 (JST)
Date: Tue, 25 Feb 1997 16:55:47 +0900 (JST)
From: Naoki Hamada <nao@sbl.cl.nec.co.jp>
Message-Id: <199702250755.QAA20017@sirius.sbl.cl.nec.co.jp>
To: freebsd-hackers@freefall.freebsd.org
Subject: MALLOC(3) writes to stderr...
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hi.

Malloc(3) of 2.2-GAMMA writes error/warning messages to stderr. There
is a daemon named jserver, which provides translations between
Japanese characters, which does close stderr before opening its
dictionary files. Sometimes jserver gets its dictionary file
completely damaged by malloc's error/warning message.

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?

- nao