office-gobmx/sal
Jan-Marek Glogowski b9d93fc47b Allow making SAL_LOG based output fatal
This introduces the [+-]FATAL marker for SAL_LOG. This way you can
set part of the matching SAL_LOG string to std::abort on match.

The example "SAL_LOG=+FATAL+WARN.vcl.scheduler-FATAL+INFO" will
abort for any "+WARN.vcl.scheduler" match, but will just print all
additional "+INFO" logs.

Change-Id: Ib77f194a78f5165e6c885c82374ae41293815ee9
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/97651
Tested-by: Jenkins
Reviewed-by: Thorsten Behrens <Thorsten.Behrens@CIB.de>
2020-07-07 14:15:04 +02:00
..
android
cppunittester
inc
osl
qa
rtl
test
textenc
util
CppunitTest_Module_DLL.mk
CppunitTest_sal_comtools.mk
CppunitTest_sal_osl.mk
CppunitTest_sal_osl_security.mk
CppunitTest_sal_rtl.mk
CppunitTest_sal_types.mk
Executable_cppunittester.mk
Executable_osl_process_child.mk
Library_lo-bootstrap.mk
Library_sal.mk
Library_sal_textenc.mk
Makefile
Module_sal.mk
README

System abstraction layer; rtl, osl and sal

rtl:
Platform independent strings

osl:
platform specific stuff, threads, dynamic loading, process, ipc, etc

Exports only C API and some inline-methods (only C++ API).