Subject: Re: port-xen/29887: sysctl kern.consdev coredumps
To: None <port-xen-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
List: netbsd-bugs
Date: 06/20/2005 22:18:02
The following reply was made to PR port-xen/29887; it has been noted by GNATS.

From: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
To: jhawk@MIT.EDU
Cc: christos@zoulas.com, gnats-bugs@NetBSD.org,
	port-xen-maintainer@NetBSD.org, netbsd-bugs@NetBSD.org,
	tech-userlevel@NetBSD.org
Subject: Re: port-xen/29887: sysctl kern.consdev coredumps
Date: Tue, 21 Jun 2005 07:17:11 +0900

 > I agree with this -- it sounds like any justification for printing
 > "(null)" is based on the fact that it is actually used, and there
 > is no good reason for fputs() to not have the same checking, other than
 > that puts() is rarely called with NULL.
 
 i really think this kind of "suppress coredump" thing is a bad practice.
 if you want explicit checks, _DIAGASSERT is for you.
 
 YAMAMOTO Takashi