Good to know! The GDB stack traces leave something to be desired, though - e.g. the way it reports closures isn't really very useful (adding source file name and line number would be really good there). But it is certainly better than nothing. Thanks!
On Fri, Nov 8, 2013 at 8:40 AM, Corey Richardson <[email protected]> wrote: > 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
