How do you suggest golang handles stack traces then? It seems Rust has the same issue by the way: https://docs.rs/error-chain/latest/error_chain/ https://docs.

How do you suggest golang handles stack traces then? It seems Rust has the same issue by the way: https://docs.rs/error-chain/latest/error_chain/ https://docs.rs/error-chain/latest/error_chain/ > If the RUST_BACKTRACE environment variable is set to anything but 0, the earliest non-foreign error to be generated creates a single backtrace If my understanding is correct, it means that you won't get stack traces for any external libraries or code that does not use this library. Because Exceptions in Java/C#/etc. are special, you will always have stack traces regardless of which code you're calling.