digitalmars.D.learn - Unit tests and segfaults
- Russel Winder <russel winder.org.uk> Dec 06 2012
Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable What is the right idiom for testing that a function call does segfault when you want it to? --=20 Russel. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder ekiga.n= et 41 Buckmaster Road m: +44 7770 465 077 xmpp: russel winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
Dec 06 2012
On 06-12-2012 10:02, Russel Winder wrote:What is the right idiom for testing that a function call does segfault when you want it to?
There is basically no portable, clean way to do that. Why are you relying on segmentation faults? It's generally speaking a very bad idea because behavior depends entirely on the platform and architecture... -- Alex Rønne Petersen alex lycus.org http://lycus.org
Dec 06 2012








=?UTF-8?B?QWxleCBSw7hubmUgUGV0ZXJzZW4=?= <alex lycus.org>