End/Termination points for Classic API tasks

[Sebastian Huber]

On 2014-06-13 19:56, Martin Galvan wrote:
> Hello everyone! I'm currently trying to figure out the "life cycle" of a
> classic API task, so to speak. I've noticed single-task applications (such as
> the hello.exe example) end after a call to _User_extensions_Thread_
> exitted (which in turn ends up in a call to _Terminate), however I'm not sure
> how tasks such as in ticker.exe end. I need to know the exact point in which
> the program ends (by that I mean where the program finishes executing and RTEMS
> starts cleaning up and calls _Terminate).

You can terminate the program with a call to exit().  You can also use atexit() 
handlers.

To catch all program termination paths in RTEMS you can use the fatal error 
extension.

http://www.rtems.org/onlinedocs/doxygen/cpukit/html/group__ScoreUserExt.html#ga04bf84979c777ddf2507923f57b554dd

The life cycle events for threads are covered with the create, start, restart, 
begin, exitted, delete and terminate extension.

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.