mirror/hdf5
2
0
Fork 0
mirror of https://github.com/HDFGroup/hdf5.git synced 2025-01-24 15:25:00 +08:00
Code Issues Packages Projects Releases Wiki Activity

[svn-r17832] Bug fix:(sort of)

Browse Source 
Some systems, like AIX poe, interpret exit(134) the same as if the process has
really been interrupted by the abort signal and prints extra messages that
confuse test script which is looking for matching output.

Solution:
Changed it to exit(6) which still has the "appearance" of an abort signal which
carries the value of 6 in Unix systems.

Tested: LLNL Up both serial and Parallel.
This commit is contained in:
Albert Cheng 2009-11-04 17:08:49 -05:00
parent 9e170a0be0
commit a81d1b4035
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
test/tcheck_version.c
View File

@ -96,7 +96,10 @@ parse(int ac, char **av)
}
/* Handler for SIGABRT - catch the abort signal supposedly from check_version()
* and exit(134). 134 would have been the return code in Unix systems.
* and exit(6). Would have used 134 is the return code in Unix systems
* but some systems (e.g., poe in AIX interprets exit(134) the same as
* if the process has really been interrupted by the abort signal and prints
* extra messages that confuse test script that is looking for matching output.
* This handles the abort signal instead letting it interrupt the OS because
* some systems may produce extra messages and/or produce core dump.
* This tries to eliminate those side effects.
@ -104,7 +107,7 @@ parse(int ac, char **av)
void
abort_intercept (int UNUSED sig)
{
HDexit(134);
HDexit(6);
}
int

2
test/testcheck_version.sh.in
View File

@ -162,7 +162,7 @@ TESTING() {
;;
*) # W/A: Warning, abort and exit non-0.
WarnMesg > $expect
expect_code=134 # Signal Abort exit code (128+6)
expect_code=6 # Signal Abort exit code (128+6)
;;
esac
fi