I made a program that just tries to access a value in a hash table that isn't there. This is using latest stable rust on Linux. Unless you're specifically debugging the backtrace mechanism itself, you don't need entries 0-12. and if you're not debugging the panic mechanism itself you don't need entries 17-26. Ironically a message is printed at the end saying that some entries have been omitted! All of these low-level internal entries are just going to be confusing for new users.
thread 'main' panicked at 'no entry found for key', game/src/main.rs:54:21
stack backtrace:
0: backtrace::backtrace::libunwind::trace
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
1: backtrace::backtrace::trace_unsynchronized
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
2: std::sys_common::backtrace::_print_fmt
at src/libstd/sys_common/backtrace.rs:78
3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
at src/libstd/sys_common/backtrace.rs:59
4: core::fmt::write
at src/libcore/fmt/mod.rs:1069
5: std::io::Write::write_fmt
at src/libstd/io/mod.rs:1504
6: std::sys_common::backtrace::_print
at src/libstd/sys_common/backtrace.rs:62
7: std::sys_common::backtrace::print
at src/libstd/sys_common/backtrace.rs:49
8: std::panicking::default_hook::{{closure}}
at src/libstd/panicking.rs:198
9: std::panicking::default_hook
at src/libstd/panicking.rs:218
10: std::panicking::rust_panic_with_hook
at src/libstd/panicking.rs:511
11: rust_begin_unwind
at src/libstd/panicking.rs:419
12: core::panicking::panic_fmt
at src/libcore/panicking.rs:111
13: core::option::expect_failed
at src/libcore/option.rs:1260
14: core::option::Option<T>::expect
at /home/mmm/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libcore/option.rs:347
15: <std::collections::hash::map::HashMap<K,V,S> as core::ops::index::Index<&Q>>::index
at /home/mmm/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libstd/collections/hash/map.rs:1023
16: game::main
at game/src/main.rs:54
17: std::rt::lang_start::{{closure}}
at /home/mmm/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libstd/rt.rs:67
18: std::rt::lang_start_internal::{{closure}}
at src/libstd/rt.rs:52
19: std::panicking::try::do_call
at src/libstd/panicking.rs:331
20: std::panicking::try
at src/libstd/panicking.rs:274
21: std::panic::catch_unwind
at src/libstd/panic.rs:394
22: std::rt::lang_start_internal
at src/libstd/rt.rs:51
23: std::rt::lang_start
at /home/mmm/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libstd/rt.rs:67
24: main
25: __libc_start_main
26: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
I made a program that just tries to access a value in a hash table that isn't there. This is using latest stable rust on Linux. Unless you're specifically debugging the backtrace mechanism itself, you don't need entries 0-12. and if you're not debugging the panic mechanism itself you don't need entries 17-26. Ironically a message is printed at the end saying that some entries have been omitted! All of these low-level internal entries are just going to be confusing for new users.