From 24e81442e6372b08c601fba69b76c29085cc5979 Mon Sep 17 00:00:00 2001 From: Joona Hakkarainen Date: Tue, 3 May 2011 15:41:55 +0300 Subject: [PATCH] Changes: Cleanup RevBy: Pertti Kellomaki --- doc/libmeegotouchboost.dox | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/libmeegotouchboost.dox b/doc/libmeegotouchboost.dox index 9e17848..b7fb1a4 100644 --- a/doc/libmeegotouchboost.dox +++ b/doc/libmeegotouchboost.dox @@ -171,7 +171,7 @@ running. You can now run your application as usual as \code invoker --type=m /usr/bin/application_binary \endcode -\_exit() should be used instead of exit() with every other booster than exec-booster +_exit() should be used instead of exit() with every other booster than exec-booster The basic difference between exit() and _exit() is that the former performs clean-up related to user-mode constructs in the library, and calls user-supplied cleanup-functions, whereas the latter performs only the kernel cleanup for the process. @@ -180,7 +180,7 @@ The function _exit() terminates the calling process "immediately". Any open file of the process are inherited by process. The exit() function causes normal process termination and the value of status is returned to the parent. -a child process should strictly use _exit() instead of a simple exit() or a normal return from main(). +A child process should strictly use _exit() instead of a simple exit() or a normal return from main(). The user level initializations of the libraries are done once when the launcher daemon loads the libraries. The launched applications are child processes of the launcher, and every time exit() is called, the corresponding cleanup actions are executed.