Are there plans to implement crash safe feature like g3log?

[ngugcx]

Awesome lib!
Are there plans to implement crash safe feature like g3log?
This is the only reason why I choose g3log other than other tools.

[odygrd]

Hello, thanks and sorry for the slow response

The reason it is not implemented is because it would restrict how the user application could handle signals.

Therefore, I don't think this should be supported by the logging library but instead it should be up to the application developer to decide how he would handle signals. If it would be a feature for sure it would be optional.

In addition handling signals in multithread applications can be a bit tricky. While it is straight forward to redirect signals to a specific thread when you send them from e.g. via the terminal, if the signals are generated by the threads themselves (e.g a SIGEVG) they won't be handled by the specified thread.

For a similar implementation to g3log you can setup your own signal handler in your application and use this on linux, remove lines 71-81 and instead call quill::flush() or similarly on windows

quill::flush() will block the current thread until all log from all threads is flushed to the file

[odygrd]

There is a crash safe feature now in quill. See https://github.com/odygrd/quill/blob/master/examples/example_signal_handler.cpp for more details