> > 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.

YAMAMOTO Takashi