G2log is an asynchronous, "crash safe" logger and design-by-contract library.
G2log is an asynchronous, "crash safe" logger and design-by-contract library. What this means in practice is that
All the slow I/O disk access is done in a background thread. This ensures that the other parts of the software can immediately continue with their work after making a log entry.
g2log provides logging, Design-by-Contract [#CHECK], and flush of log to file at shutdown. Buffered logs will be written to file before the application shuts down.
It is thread safe, so using it from multiple threads is completely fine.
It is CRAsH SAFE, in that it will catch certain fatal signals, so if your application crashes due to, say a segmentation fault, SIGSEGV, or some other fatal signals it will log and save to file this crash and all previously buffered log entries before exiting.
It is cross platform. For now, tested on Windows7 and Ubuntu
On Ubuntu a caught fatal signal will generate a stack dump to the log. This is not yet available on Windows due to the platforms complexity when traversing the stack. Stack dump on Windows will be released later and a beta is available on request.
G2log is used in commercial products as well as hobby projects since early 2011. The code is given for free as public domain. This gives the option to change, use, and do whatever with it, no strings attached.
The stable version of g2log is available at https://bitbucket.org/KjellKod/g2log The in-development g2log where new features are tried out is available at https://bitbucket.org/KjellKod/g2log-dev ongoing and released features can be
seen at https://bitbucket.org/KjellKod/g2log-dev/wiki/HomeThe latest generation of "g2log", named g3log has all the features of g2log with the addition that custom made "log sinks" can be added. It can be seen at:
https://bitbucket.org/KjellKod/g3log
