while technically possible (on both machine and OS level), termination due to SIGSEGV cannot be prevented maybe the test could be rewritten to spawn a subprocess and check its exit status (of 11)