Date: Tue, 27 Apr 2021 21:56:09 +0100
On Tue, 27 Apr 2021 at 21:04, Андрей Некрашевич via Std-Proposals <
std-proposals_at_[hidden]> wrote:
> > Presumably this particular implementation won't work if libcxxabi is
> statically linked
>
> Yes, that's right. But as the paper says - `libsfe` is just a prototype
> to show that we can add `std::stacktrace::from_current_exception` without
> breaking ABI. Library does not pretend to be a release implementation.
>
There is some overhead in taking a stack trace, even if you defer symbol
(and source location) resolution until it is used. Are you proposing that
the runtime call backtrace / CaptureStackBackTrace on every throw?
Will the stack trace be attached to std::exception_ptr?
std-proposals_at_[hidden]> wrote:
> > Presumably this particular implementation won't work if libcxxabi is
> statically linked
>
> Yes, that's right. But as the paper says - `libsfe` is just a prototype
> to show that we can add `std::stacktrace::from_current_exception` without
> breaking ABI. Library does not pretend to be a release implementation.
>
There is some overhead in taking a stack trace, even if you defer symbol
(and source location) resolution until it is used. Are you proposing that
the runtime call backtrace / CaptureStackBackTrace on every throw?
Will the stack trace be attached to std::exception_ptr?
Received on 2021-04-27 15:56:23