Subject: Re: [boost] Is there interest in a collection of call stack utilities?
From: Shakti Misra (shakti.misra.study_at_[hidden])
Date: 2013-03-03 23:28:55
I havent seen the source yet but a quick question. The compiler list says
visual studio 2012 and gcc 4.7+. Is this library tied to these version? At
least I would love to have this functionality in a few earlier versions of
VC and GCC. Clang would be nice too.
On Mon, Mar 4, 2013 at 6:45 AM, Alexander Lamaison <awl03_at_[hidden]>wrote:
> Mathias Gaunard <mathias.gaunard_at_[hidden]> writes:
> > On 03/03/13 15:20, Alexander Lamaison wrote:
> >> Mathias Gaunard <mathias.gaunard_at_[hidden]> writes:
> >>> On 03/03/13 13:14, Alexander Lamaison wrote:
> >>>> Surely the idea is to get back-traces from deployed software? You
> >>>> use your debugger there.
> >>> Just get the core dump and import it in your debugger.
> >> From my users? I'm not sure many of them know how to do this. Hell, I
> >> don't even know how to do this.
> >> In any case, aren't they only produced if a program crashes? What I
> >> often need is the backtrace when my program has caught an exception and
> >> shown users an error message.
> > How do you think errors are reported with software like Firefox?
> Firefox only reports crashes, not arbitrary errors. I've no idea how it
> does it (Google have a library you can use to add the same functionality
> to your own project) but that's not the use-case where Artyom's code
> would be useful.
> Instead, his code is used to get source information for errors that
> occur during normal program operation. Core dumps (crashes) should be a
> vanishingly rare event in deployed software, but errors happen as part
> of normal program behaviour. When the cause of the error is a bug in
> the software rather than user error or environment, it would be
> invaluable if the user could provide a back-trace as part of their bug
> Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk