Subject: Re: port-xen/29887: sysctl kern.consdev coredumps
To: None <,,>
From: YAMAMOTO Takashi <>
List: netbsd-bugs
Date: 06/21/2005 00:06:02
The following reply was made to PR port-xen/29887; it has been noted by GNATS.

From: YAMAMOTO Takashi <>
Cc: jhawk@MIT.EDU,,,,,
Subject: Re: port-xen/29887: sysctl kern.consdev coredumps
Date: Tue, 21 Jun 2005 09:04:49 +0900

 > > i really think this kind of "suppress coredump" thing is a bad practice.
 > > if you want explicit checks, _DIAGASSERT is for you.
 > I disagree. I think suppressing coredumpes is an excellent idea, where 
 > reasonable.
 > My day job is working on a shipping product. Core dumps are bad. Core 
 > dumps generate customer service issues, and impact the reliaility of the 
 > product. I would much rather have customers reporting logs like "Error X 
 > with client (null)" than passing back stack traces.
 yes, "(null)" can be useful or dangerous, depending on the calling context.
 however, there is no way for a library to know which is the case.
 fixing your product is appropriate because you know it's useful there.