Better stack traces #521

Activity

1. RalfJung

   added

   C-enhancementCategory: a PR with an enhancement or an issue tracking an accepted enhancementCategory: a PR with an enhancement or an issue tracking an accepted enhancement

   A-uxArea: This affects the general user experienceArea: This affects the general user experience

   on Nov 17, 2018
2. RalfJung commented on Mar 28, 2020

   

   RalfJung

   on Mar 28, 2020

   Last edited by RalfJung

   MemberAuthor

   More actions

   Backtraces are better now since we don't show code outside the current crate.

   But I still find one thing pretty confusing: we print things like

      = note: inside call to `std::alloc::alloc` at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/liballoc/alloc.rs:172:35
      = note: inside call to `<std::alloc::Global as std::alloc::AllocRef>::alloc` at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/liballoc/alloc.rs:225:15
      = note: inside call to `alloc::alloc::exchange_malloc` at /home/r/.rustup/toolchains/miri/lib/rustlib/src/rust/src/liballoc/rc.rs:327:49
   

   Usually, backtraces pair up a function name with the relevant file and line inside that function. But Miri pairs up a function name with the file and line of its caller. I think that is unnecessarily confusing.
3. RalfJung

   added

   E-medium

   on Mar 28, 2020
4. bors

   added a commit that references this issue on Apr 2, 2020

   Auto merge of #1283 - RalfJung:backtrace, r=RalfJung

   ...

   ed14328
5. bors

   closed this as completedin ed14328on Apr 2, 2020