Programmatic access to the call stack in C++
eli.thegreenplace.net
eli.thegreenplace.net
Anyhow, there's pretty good support for stack traces on Win64. For 32 bit it's less good. https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...
But I'm fairly sure that these days os x uses libcxx which uses libunwind
My biggest problem with "standard" libunwind is how slow it is compared to a whole loop against the registers (which of course isn't reliable with -fomit-frame-pointer). IIRC, the gcc's call to backtrace actually parses DWARF to work around this (and thus is super slow).