Base your stack tracing / "symbolization" on Boost stack_trace

[eyalroz]

The roadmap includes the following item:

• symbolizer - for a stack trace - when an assertion fails - and it's in a user function with some deep callstack away from the current test case - how to know the exact code path that lead to the failing assert.

Facebook's folly is by now pretty old. Instead, you should base this work on Antony Polukhin's excellent and extensive work for the Boost Stack Trace library (now officially released as part of Boost, and with documentation, too).

[onqtam]

Good to know - I'll most likely use that!

[eyalroz]

I should mention that last year I created a de-boostified version of libstacktrace.