[Valgrind-users] How to include the Valgrind stack traces in a stand-alone debug version?

[Martin L. <ml...@uc...>]

Hello,

I think the Valgrind stack tracer is pretty great and I would like to use
it as a substitute for `backtrace` in my C++ debug builds.

A blog post by Nicholas Nethercote (Using Valgrind to get stack traces)
describes a similar idea:
https://blog.mozilla.org/nnethercote/2011/01/11/using-valgrind-to-get-stack-traces/

However, while this is already fairly elegant, I am wondering whether this
can be done without invoking the program under valgrind.

If the Valgrind stack tracer were a simple #include that would be best.
Alternatively, a means of including any necessary valgrind framework into
the debug build would be helpful. I appreciate your feedback.

Regards,
Martin