Factory: safe construction of object before thread start

Triggered by g3log::LogWorker after receiving a FATAL trigger which is LOG(FATAL), CHECK(false) or a fatal signal our signalhandler caught. --- If LOG

helper for fatal CHECK

helper for fatal exception (windows only)

helper for fatal LOG

helper for fatal signal

The actual log receiving function

OK: The code below isn't pretty but it works. Lots and lots of log entries to keep track of!

helper for normal

Fatal call saved to logger. This will trigger SIGABRT or other fatal signal * to exit the program. After saving the fatal message the callin

restores the signal handler back to default

For windows exceptions this might ONCE be set to false, in case of a windows exceptions and not a signal

called for fatal signals SIGABRT, SIGFPE, SIGSEGV, SIGILL, SIGTERM

Dump of stack,. then exit through g3log background worker ALL thanks to this thread at StackOverflow. Pretty much borrowed from: Ref: http://stackover

helper function: retrieve stackdump from no excisting exception pointer

\return immediately, with true if successful retrieval

Unhandled exception catching

logCapture is a simple struct for capturing log/fatal entries. At destruction the * captured message is forwarded to background worker. * As a safety