Subject: Re: [boost] Checking interest in stacktrace library
From: Rob Stewart (rstewart_at_[hidden])
Date: 2016-06-19 06:44:17
On June 18, 2016 6:34:38 AM EDT, Antony Polukhin <antoshkka_at_[hidden]> wrote:
>I've got some prototype for getting stack traces:
>Is there interest in it?
>What functionality would you like to have in it?
IME, you need to filter a few layers of backtrace corresponding to your code. That is, don't reveal your function calls, just those of the caller.
The option to look up file and line number is valuable.
An option to control the call depth would be valuable.
Rendering the backtrace using output iterators, or into a container, would give users maximum control over how to use the information. Rendering into a string would be a simpler form of that. (std::ostringstream allows for that, of course, but is a heavy tool to do so.)
Demangling is helpful.
How will you signal unsupported platforms?
(Sent from my portable computation engine)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk