I am not able to think of any use-case where filtering the stacktrace data
would be useful.
It is already possible to put the stacktrace into the log using C++ streams
- boost stacktrace provides
std::basic_ostream< CharT, TraitsT > &
operator<<(std::basic_ostream< CharT, TraitsT > & os,
I've been working on adding in stacktrace support to Log4cxx using
Boost stacktrace. One of my objectives with this is to make this
entirely optional, such that both Log4cxx needs to have support for
Boost stacktrace and the client code needs to enable it, so by default
a stacktrace is not
