Using the given context, fill in all the stack frames. Which then later can be interpreted to human readable text

Retrieves all the symbols for the stack frames, fills them within a text representation and returns it

The default, initial, handling to send a 'fatal' event to g3logworker * the caller will stay here, eternally, until the software is aborted

extract readable text from a given stack frame. All thanks to using SymFromAddr and SymGetLineFromAddr64 with the stack pointer

Installs FATAL signal handler that is enough to handle most fatal events on *NIX systems

SIGFPE, SIGILL, and SIGSEGV handling must be installed per thread on Windows. This is automatically done if you do at least one LOG(...) call you can

Yes a double lookup: first for isKnownException and then exceptionIdToText for vectored exceptions we only deal with known exceptions so this tiny ove

The function above 'tryToKillWithIllegalPrintout' IS system / compiler dependent. Older compilers sometimes did NOT generate a segmentation fault as e

This mimics the original "std::put_time(const std::tm* tmb, const charT* fmt)" This is needed since latest version (at time of writing) of gcc4.7 does

explicitly copy of all input. This is makes it possibly to use g3log across dynamically loaded libraries * i.e. (dlopen + dlsym) */

Get weak_ptr access to the sink(). Make sure to check that the returned pointer is valid, auto p = sink(); auto ptr = p.lock(); if (ptr) { .... } ref:

on Ubunti this caused get a compiler warning with gcc4.6 from gcc 4.7.2 (at least) it causes a crash (as expected) On windows it'll probably crash too

Try to retrieve, if no items, wait till an item is available and try again

helper for setting the normal log details in an entry

Called from crash handler when a fatal signal has occurred (SIGSEGV etc)

default operator needed for std::map compliance

* capturef, used for "printf" like API in CHECKF, LOGF, LOGF_IF * See also for the attribute formatting ref: http://www.codemaestro.com/reviews/18 */