Rust's backtraces moving to be native Rust: https://github.com/rust-lang/rust/pull/74682/commits/06d565c967bfb7c6ff52a991bbe47b4a2a25de3e
This prevents malformed DWARF info leading to security issues, an avenue for vulnerabilities I'd not considered before. https://twitter.com/Brittain_Ben/status/1288193388588740615
miniblog.
Related Posts
12
Claude asked me a question today: was I looking for an Emacs plugin (because I was talking about elisp) or a Rust program (because I have configured Rust preferences)?
I'm really impressed, it's rare to see LLMs ask follow-up questions.
(I wanted Emacs in this case.)
15
I see that *up has become an increasingly common name for toolchain installers: rustup, ghcup, even juliaup.
I think Rust was the first to use this terminology? I'm curious how similar the different *up tools are.
2
I would have thought that invoking a C compiler would be a solved problem. Looking at Rust's cc crate there's a remarkable long tail of corner cases to fix.
Exotic CPUs, microarchitectures, compiler differences, operating system differences, etc.