bjorn3

GNU libiberty (as used by binutils and gdb) has support for demangling both the current legacy symbol mangling scheme and the new v0 symbol mangling scheme. In any case if...

> Rust seems to be still using the old modified Itanium mangling scheme, and that can be demangled fairly well with the existing C++ demangler. Indeed. > We need to...

https://www.fsf.org/bulletin/2014/spring/copyright-assignment-at-the-fsf > Thus, we grant back to contributors a license to use their work as they see fit. This means they are free to modify, share, and sublicense their own...

As I understand it they give you a license back that allows you to sublicense it under any terms you want. I can't easily find the exact legal text though.

That is a rust crate which uses the rustc_demangle crate for demangling rust symbols: https://github.com/getsentry/symbolic/blob/56349e9686a4dc655d0b9e9c0ccfff82ca4e95d7/symbolic-demangle/src/lib.rs#L278

> This only adds Windows for now because it is Rust cannot be profiled on Windows backtrace-rs is not magic. You can use the same api's as for C/C++ stack...

Could we always have the unwind tables, but just omit the landingpads when using `-Cpanic=abort`? (Maybe gating it on `-Cdebuginfo`?)

You can put it in the `rustflags` field of `.cargo/config.toml`.

> We'll likely need to add a fallback in gimli where if a symbol doesn't hit the cache of libraries we know about we check again to see if any...

I think this shouldn't be enabled by default at least. Having the executable directly download it would cause bloat and would expose it to (more) untrusted data (which means it...