Hi! > When testcase is killed by unexpected signal, usually it just prints > signal's value. > fcntl30 1 TBROK : unexpected signal 2 received (pid = 6714). > fcntl30 2 TBROK : Remaining cases broken > > Here we also print signal's name to output more informative message. > fcntl30 1 TBROK : unexpected signal SIGINT(2) received (pid = > 9872). > fcntl30 2 TBROK : Remaining cases broken > > In this patch, we also add two new tst_ functions to convert errno or signal > to its name. The prototype is below: > const char *tst_strsig(int sig); returns signal name given signal number > const char *tst_strerrno(int err); returns errno name given errno number
I've added two simple tests to lib/tests/ and pushed, thanks. Will you send a patch to add these two to Test Writing Guidelines? -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
