Kemyt b66ddb30a1 Change signal raised by fatal event handling ...

Segmentation fault doesn't seem like an appropriate choice for handling
Fatal events. SIGTERM allows for cleaner exit (if signal handler is
implemented).

2021-03-02 11:34:20 +01:00

..

docs

mstarch: final preparations for automatic C++ API generation

2020-08-26 22:23:49 -07:00

CMakeLists.txt

mstarch: fixing shared lib build to resolve #607

2020-10-07 14:13:10 -07:00

FatalHandler.mdxml

Initial check-in

2017-06-16 08:25:38 -07:00

FatalHandlerComponentAi.xml

mstarch: finalizing Autocoders -> Autocoders/Python move

2019-02-20 12:19:35 -08:00

FatalHandlerComponentBaremetalImpl.cpp

mstarch: fixing fatal handler

2019-11-14 16:24:08 -08:00

FatalHandlerComponentCommonImpl.cpp

Refactor FW_OBJECT_NAMES switches and fix building without object names

2020-10-07 17:19:05 -07:00

FatalHandlerComponentImpl.hpp

Refactor FW_OBJECT_NAMES switches and fix building without object names

2020-10-07 17:19:05 -07:00

FatalHandlerComponentLinuxImpl.cpp

Change signal raised by fatal event handling

2021-03-02 11:34:20 +01:00

FatalHandlerComponentVxWorksImpl.cpp

mstarch: fixing up new Logger, LogAssert for #208

2019-05-13 22:10:14 -07:00

Makefile

Initial check-in

2017-06-16 08:25:38 -07:00

mod.mk

mstarch: more header cleaning for issue: #189

2019-04-18 14:12:02 -07:00