summaryrefslogtreecommitdiff
path: root/testsuites/sptests/spfatal28 (follow)
AgeCommit message (Collapse)Author
2019-11-12sptests: Avoid include path magicSebastian Huber
Update #3818.
2018-10-05tests: Use rtems_task_exit()Sebastian Huber
Update #3533.
2018-04-10testsuite/sptests: Merged nested Makefile.am files into one Makefile.amChris Johns
This change is part of the testsuite Makefile.am reorganization. Update #3382
2016-12-09score: Remove fatal is internal indicatorSebastian Huber
The fatal is internal indicator is redundant since the fatal source and error code uniquely identify a fatal error. Keep the fatal user extension is internal parameter for backward compatibility and set it to false always. Update #2825.
2016-11-03score: Conditionally enable thread resource countSebastian Huber
Maintain the thread resource count only in debug configurations. This is a performance optimization for non-debug configurations.
2014-04-03score: PR788: Add INTERNAL_ERROR_RESOURCE_IN_USESebastian Huber
Issue a fatal error in case a thread is deleted which still owns resources (e.g. a binary semaphore with priority inheritance or ceiling protocol). The resource count must be checked quite late since RTEMS task variable destructors, POSIX key destructors, POSIX cleanup handler, the Newlib thread termination extension or other thread termination extensions may release resources. In this context it would be quite difficult to return an error status to the caller. An alternative would be to place threads with a non-zero resource count not on the zombie chain. Thus we have a resource leak instead of a fatal error. The terminator thread can see this error if we return an RTEMS_RESOURCE_IN_USE status for the rtems_task_delete() for example.