/*
 *  test_stop.sli
 *
 *  This file is part of NEST.
 *
 *  Copyright (C) 2004 The NEST Initiative
 *
 *  NEST is free software: you can redistribute it and/or modify
 *  it under the terms of the GNU General Public License as published by
 *  the Free Software Foundation, either version 2 of the License, or
 *  (at your option) any later version.
 *
 *  NEST is distributed in the hope that it will be useful,
 *  but WITHOUT ANY WARRANTY; without even the implied warranty of
 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 *  GNU General Public License for more details.
 *
 *  You should have received a copy of the GNU General Public License
 *  along with NEST.  If not, see <http://www.gnu.org/licenses/>.
 *
 */

/* BeginDocumentation
Name: testsuite::test_stop - test if SLI returns exit code 126 when executing a file with a software interrupt.

Synopsis: (test_stop) run -> 

Description: 
This script calls the SLI command `stop` that is not handled by any
user error handler. This is a rarely used feature of SLI called
"software interrupt". This scipt is used to test if SLI quits with
exit code 126 after executing a file that causes a software
interrupt.

Author: Ruediger Kupper

FirstVersion: 03-jul-2008

Remarks:
Yes, this script is really meant to fail due to an unhandled software interrupt.

SeeAlso: testsuite::test_pass, testsuite::test_fail, testsuite::test_stop, testsuite::test_goodhandler,  testsuite::test_lazyhandler, testsuite::test_badhandler
*/

% Yes, this script contains a stop without error handler. That's intentional.
% And no, there shall be no stopped context around this error. Really.

%call unhandled stop (cause software interrupt):
stop
