arm64: Changes to register and stack dumps
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] arm64: Changes to register and stack dumps
Quoted 7 lines · Laura Abbott
Quoted 6 lines · Will Deacon
This handful of patches makes some significant changes to how we print register/stack dumps and brings us inline with recent changes to x86. The main changes are that we no longer print out the 'Exception stack:' section and PC/LR values are resolved to a symbol+offset format where possible.
Quoted 7 lines
Quoted 2 lines
Feedback welcome.
In very petty complaints, I can no longer just use the PC/LR with addr2line. Yes I can use gdb or one of the scripts but that's a few more steps when I'm doing debugging on my own. Like I said, very minor and overall this is good for both security and alignment.
Understood. scripts/faddr2line seems to do a reasonable job, but I agree that it's a little annoying that you have to do some pointer arithmetic if you want to e.g. locate disassembly in objdump. Setting KALLSYMS=n will give you the addresses if you *really* want them.
Quoted 4 lines
I ran this through several of the LKDTM tests and the backtraces looked fine. You're welcome to add
Tested-by Laura Abbott <[email protected]>
Thanks, Laura.
Will