Subject: Re: DIAGASSERT in cryptographic functions.
To: None <tech-userlevel@netbsd.org>
From: Christoph Badura <bad@oreilly.de>
List: tech-userlevel
Date: 09/17/1999 00:02:11
sommerfeld@orchard.arlington.ma.us (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.
--
Christoph Badura www.netbsd.org
Anything that can be done in O(N) can be done in O(N^2).
-- Ralf Schuettau (after looking at a particular piece of code)