Better kernel crash call traces?

[petershh]

Right now, only addresses are printed in an event of crash, so one needs to run llvm-symbolize on those to get names of the functions involved. I think it would be good if this data was printed automatically. I'm thinking of linux's call trace as an example.

C++ mangled names may complicate things though.

[heatd]

Okay so: this isn't truly a real issue. We already symbolize backtraces (that you haven't seen a symbolized one make me happy!) The backtrace you're talking about (on your laptop) is so early we haven't set up symbols yet. We could symbolize things in another way so we could do this earlier, and it'd be good (and needed if we ever do another boot protocol). See how linux does kallsyms