You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CA-423574: avoid losing backtraces when reraising (#6896)
Xenopsd reraises some exceptions in a different, simplified form. But
this needs to retain the stacktrace from the original place that raised
the first exception, otherwise it might be hard to debug.
This is a followup to [the previous PR
](#6891), I found a few more
places that would lose a stacktrace while working on another code change
in the area.
Recommended to review with 'ignore whitespaces' enabled.
To avoid losing the backtrace we need to mark it with
`Backtrace.is_important` and to use `Backtrace.reraise` instead of
`raise`.
(or we could do this using purely the stdlib with
`Printexc.get_raw_backtrace()` and `Printexc.raise_with_bt`, but the
rest of the code around here uses Backtrace already, so for consistency
use that)
0 commit comments