18 Dec
2016
18 Dec
'16
10:39 p.m.
On 19/12/2016 06:26, Peter Dimov wrote:
- the part that captures a stack trace and the part that resolves it to function/file/line should be separate, and usable without each other.
- ideally, both ought to be async safe, or as async safe as possible on the target architecture.
Agreed for capturing. But I don't think there should be any requirement to make resolving a trace be async-safe. There's rarely going to be anything useful you could do with such a trace that would also be async-safe; it'd be better to require that this be done in regular context instead. And I doubt all (any?) platforms would be capable of doing so, anyway.