Don't use the setenv function after fork

Authored by jpalecek on Jun 7 2020, 9:23 AM.

Description

Don't use the setenv function after fork

Summary:
Ideally, you should not use any non-async-signal-safe functions after fork(), because the situation after fork is very similar to the situation in the signal handler. In kcrash, we are in signal handler before fork, so we shouldn't use setenv even before fork. This patch however emulates setenv using static memory so should be safe.

Depends on D29809
Signed-off-by: Jiří Paleček <jpalecek@web.de>

Reviewers: Frameworks, dfaure

Reviewed By: dfaure

Subscribers: bruns, apol, anthonyfieroni, kde-frameworks-devel

Tags: Frameworks

Differential Revision: https://phabricator.kde.org/D29810

Details

Committed
dfaureJun 7 2020, 9:24 AM
Reviewer
dfaure
Differential Revision
D29810: Don't use the setenv function after fork
Parents
R285:dfae07a8ed40: Fix segfault on no restart args
Branches
Unknown
Tags
Unknown
References
tag: v5.71.0-rc3