Entirely unrelated. Do note that we have stack traces *now*, as long
as you're using gdb to get them :). Break on `rust_begin_unwind` or
"catch throw".

On Fri, Nov 8, 2013 at 1:27 AM, Oren Ben-Kiki <[email protected]> wrote:
> Does ditching segmented stacks mean we can start getting a stack trace when
> a task `fail!`s? Or is this an unrelated issue?
>
> The lack of stack traces is extremely tedious when debugging failed
> assertions...
>
> _______________________________________________
> Rust-dev mailing list
> [email protected]
> https://mail.mozilla.org/listinfo/rust-dev
>
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev

Reply via email to