New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/internal/obj/arm64: add frame pointers #10110
Comments
Replaces 4ad/go#101 |
And Apple's ARM64 abi mandates frame pointer.
|
Too late for Go 1.5. |
https://go-review.googlesource.com/#/c/20193/ fixes backtrace in gdb under arm64. And it turns out that the break backtrace is caused by incorrect handling ra position relative to CFA during function call in DWARF '.debug_frame' under arm64. I find frame pointer is still needed in linux perf tool to unwind stack when using "--call-graph fp". But it could be workarounded by telling perf unwind stack using DWARF info. |
Yes, we we add frame pointers in 1.8. |
Change https://golang.org/cl/61511 mentions this issue: |
RISC architectures fare much worse in gdb compared to x86. Right now we can't have stack traces in gdb, on arm64. Adding frame pointers would fix this.
The text was updated successfully, but these errors were encountered: