End/Termination points for Classic API tasks
martin.galvan at tallertechnologies.com
Tue Jun 17 13:45:58 UTC 2014
Thanks a lot. Is it safe to assume every program will, at some point, call
_Terminate? (unless of course it's running indefinitely)
On Mon, Jun 16, 2014 at 4:08 AM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:
> 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
>> how tasks such as in ticker.exe end. I need to know the exact point in
>> the program ends (by that I mean where the program finishes executing and
>> 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.
> 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.
Taller Technologies Argentina
San Lorenzo 47, 3rd Floor, Office 5
Phone: 54 351 4217888 / +54 351 4218211
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users