[Feature] stack trace printing in signal handlers

Currently in DMLC core the utility for printing stacktrace (and demangling) are the following:

https://github.com/dmlc/dmlc-core/blob/ebcaa42d0b7271265e6a02ff468c6753a8fbecdb/include/dmlc/logging.h#L49-L96

The problem with them is that they can't be used safely in asynchronous signal handlers, for which [non-reentrant functions](https://www.ibm.com/developerworks/library/l-reent/) are required.

According to [boost](https://www.boost.org/doc/libs/1_67_0/doc/html/stacktrace/getting_started.html#stacktrace.getting_started.handle_terminates_aborts_and_seg), there isn't a safe way to get stacktrace that's portable. On the other hand, one was described in this [blog](https://oroboro.com/stack-trace-on-crash/). The downside is that on windows it relies on [StackWalker](https://www.codeproject.com/Articles/11132/Walking-the-callstack-2). There may be better, more modern ways to achieve this that I missed.