Subject: Re: [boost] [Backtrace] Any interest in portable stack trace?
From: Rob Riggs (rob_at_[hidden])
Date: 2010-10-22 10:26:33
On 10/21/2010 06:40 AM, Artyom wrote:
> Hi All,
>> One recommendation, decide early on limitations.
>> I recommend to choose from the beginning:
>> - whether it should work in asynchronous interrupts such as signal handlers,
>> - whether it should work when the program is unstable, such as memory fault
>> handlers, and
>> - how good a performance to expect.
> Very Good idea:
> Limitations of use:
> 1. No it is not asynchronous interrupts safe
> 2. It would not likely work when the application is unstable or as serious
> 3. The trace collection is expected to be very fast (as walking on linked list)
> 4. The trace printing may be quite slow and costly, expected to be used quite
Will the trace printing function use information provided by debuginfo
packages on Linux?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk