Previous: conditions child abnormal, Up: conditions child [Contents][Index]
We can use the child failure exit status exceptional–condition object–type to signal the
termination of a child process with a non–zero status; this happens when the process is terminated
by a call to the exit()
function with a non–zero argument or by simply returning non–zero
from the main()
function. We can instantiate this type and also derive new types from it. To
catch this exceptional condition we can do:
cce_location_t L[1]; if (cce_location(L)) { if (cctests_condition_is_child_failure_exit_status(cce_condition(L))) { CCTESTS_PC(cctests_condition_child_failure_exit_status_t, C, cce_condition(L)); do_something_with(C); } cce_run_catch_handlers_final(L); } else { do_something(L); cce_run_body_handlers(L); }
Type of data structure representing the exceptional–condition descriptor. It has the following public fields:
cce_descriptor_t descriptor
The condition descriptor’s base values.
The parent of this type descriptor is the one referenced by
cctests_descriptor_child_failure_ptr
, Child failure.
Type of data structure representing the exceptional–condition object. It has the following public fields:
cctests_condition_child_failure_t child_failure
The condition object’s base values.
Set the parent of the descriptor referenced by D to the descriptor of the
exceptional–condition object–type cctests_condition_child_failure_exit_status_t
.
Initialisation function for the condition object. This function is meant to be called from the
initialisation function of sub–types of cctests_condition_child_failure_exit_status_t
.
Return a pointer to exceptional–condition object of type
cctests_condition_child_failure_exit_status_t
made opaque in the type cce_condition_t
.
Return true
if C if of type cctests_condition_child_failure_exit_status_t
; otherwise
return false
.
Previous: conditions child abnormal, Up: conditions child [Contents][Index]
This document describes version 0.4.1-devel.1 of CCTests.