Hi,
I have done something along those lines a while back for *nix. If
libunwind is available at build time then this code will print a
gdb-style backtrace on abort:
https://github.com/zeromq/libzmq/blob/master/src/err.cpp#L391
Need to be careful with core dumps and backtraces as they might expos
Hi,
Thinking about it, I may change my mind. It may be interesting to be able to
generate a core dump (mini dump) in the zmq_assert statements if it can be
switched on or off, e.g. by a define or even context property. I think this
would help finding issues in ZeroMQ.
Cheers,
Jens
--
Dr. Jens
