From 417b4156e2f95d726d148d17351c8c90e595613d Mon Sep 17 00:00:00 2001 From: Saya Sugiura Date: Tue, 26 Mar 2019 16:47:37 +0900 Subject: doc: Do not allow DLT usage in forked child (#95) Update the documents to adapt to behavior change of forked child. Relates to following commit: 18321f3 libdlt: Do not allow DLT usage in forked child (#95) Signed-off-by: Saya Sugiura --- doc/dlt_cheatsheet.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'doc/dlt_cheatsheet.txt') diff --git a/doc/dlt_cheatsheet.txt b/doc/dlt_cheatsheet.txt index 736142b..8babc2a 100644 --- a/doc/dlt_cheatsheet.txt +++ b/doc/dlt_cheatsheet.txt @@ -75,7 +75,8 @@ int main(int argc, const char\* argv\[\]) ---- .Important notes: -* If your application uses fork(), you may not call DLT_REGISTER_APP before fork(). And fork() should never be called after DLT_REGISTER_APP. This is because of state information and inter process communication channel to daemon would be copied to new process, but threads would be not. If you are not sure where you are calling DLT_REGISTER_APP() the first time, you can initialise the DLT user library by calling the initialisation routine directly. +* DLT may not be used in a forked child until a variant of exec() is called, + because DLT is using non async-signal-safe functions. ---- dlt_user_init(); ---- -- cgit v1.2.1