Subject: Re: DIAGASSERT in cryptographic functions.
To: None <firstname.lastname@example.org>
From: Simon Burge <email@example.com>
Date: 09/17/1999 17:46:54
Christoph Badura wrote:
> firstname.lastname@example.org (Bill Sommerfeld) writes:
> >My experience has taught me that the best way to keep defects from
> >piling up in the development cycle (which is where tools like
> >DIAGASSERT are most useful) is to make detected bugs *hurt* (and cause
> >the program to abort and dump core);
> ISTR Luke saying something about not wanting to have critical programs dump
> core on him. One possible solution is to fork() and let the child dump core.
One solution to with would be to compile critical programs statically
against non-diagassert libraries. I think tcsh was the program Luke was