On Tue, 2012-12-11 at 18:58 +0100, Jonathan M Davis wrote: […] > I'd argue that if you want an error condition that you test for, you should > actually do something in your code that generates an error condition (e.g. > throw an exception) and that it really makes no sense to test for segfaults. > That's not really an error condition. That just means that your code is > broken. And such cases aren't generally worth testing for IMHO.
I appreciate where you are coming from with respect to general testing strategy, and am basically in agreement with what you say. However in this specific case a segfault is just another exception. In terms of recursion the exception is "recursion stack limit reached" it just happens to be spelt "segfault" […] -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Road m: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
