Ashod Nakashian 4e9b836ea6 wsd: always use Util::forcedExit to properly cleanup ... We need to flush and shutdown logging before exiting, so we can't use _exit/_Exit directly. In addition, with profiling (e.g. code-coverage) we must flush the profile data, lest it's all for naught. Change-Id: I726c5a2f4e699c17dd0d7d5b1c86d856e0118b3c Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>		2022-08-02 07:51:52 -04:00
..
Config.cpp	wsd: always use Util::forcedExit to properly cleanup	2022-08-02 07:51:52 -04:00
ConfigMigrationAssistant.cpp
Connect.cpp	wsd: always use Util::forcedExit to properly cleanup	2022-08-02 07:51:52 -04:00
COOLWebSocket.hpp
KitClient.cpp	wsd: always use Util::forcedExit to properly cleanup	2022-08-02 07:51:52 -04:00
map.cpp
mount.cpp
Replay.hpp	wsd: always use Util::forcedExit to properly cleanup	2022-08-02 07:51:52 -04:00
Stress.cpp	wsd: always use Util::forcedExit to properly cleanup	2022-08-02 07:51:52 -04:00
Tool.cpp
WebSocketDump.cpp